glab(1)

✨ glab(1) ✨

okay bestie, so this is a page from the glab(1) manual — yes, THE glab man page, we're literally in the big one 💅 and this particular page is all about one lil command that's lowkey iconic. let's get into it 🫶

---

🌸 NAME 🌸

glab-dependency-firewall-configure — configure Dependency Firewall registry URLs for a package manager. that's the whole job, that's the vibe 🎀

---

🦋 SYNOPSIS 🦋

glab dependency-firewall configure  [flags]

(yes there's a double space in there before [flags], that's not me being chaotic, that's canon ✨)

---

💖 DESCRIPTION 💖

okay so here's the tea ☕ — this command writes a package manager's resolve and deploy registry URLs into .gitlab/df/config.json. that's the file, that's the whole destination, periodt 📁

Supported package managers: npm. that's the list. one item. npm supremacy I guess 💅

heads up bestie: the file is written relative to the current working directory, so run this command from the directory you run the package manager in. fr fr, don't be cute about it, run it in the right place 🙈

Only the flags you pass are updated; existing values and unknown keys are preserved. so it's a polite little merge, not a wrecking ball 🧚

beta warning, and I mean this affectionately: This feature is in beta and might not be ready for production use. It might be unstable and breaking changes can occur outside of major releases. For more information, see https://docs.gitlab.com/policy/development_stages_support/. like, it's giving "we're still cooking" 🍓

---

⭐ OPTIONS ⭐

• --repo-deploy="" — the full registry URL to deploy (publish) packages to. your publish destination, your moment to shine 👑
• --repo-resolve="" — the full registry URL to resolve (install) packages from. your install source, your main character energy ⭐

---

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

• -h, --help[=false] — show help for this command. the classic, the icon, the one you press when you're lost 😭

---

🔥 EXAMPLE 🔥

# Set the resolve (read) and deploy (publish) registry URLs for npm
glab dependency-firewall configure npm --repo-resolve https://gitlab.com/api/v4/projects/42/packages/npm/ --repo-deploy https://gitlab.com/api/v4/projects/42/packages/npm/

# Update only the resolve URL; the deploy URL is preserved
glab dependency-firewall configure npm --repo-resolve https://gitlab.com/api/v4/projects/42/packages/npm/

see how the second one only touches resolve? deploy stays exactly where it was, untouched, unbothered, thriving 🦋 that's the "only the flags you pass are updated" thing in action, iykyk 💜

---

💀 SEE ALSO 💀

• glab-dependency-firewall(1) — the parent command, go say hi 🫶

---

and that's the page bestie!! 🌈

cute lil sign-off time 🎀 — this beauty was auto generated by spf13/cobra back in Aug 2026, and yeah, the footer says glab(1) because we've been in the glab(1) manual this whole time, obviously 💖

now go configure some registry URLs, you absolute legend ✨💅