| title | `glab dependency-firewall bundle` |
|---|---|
| stage | AI Clients |
| group | Developer Clients |
| info | To determine the technical writer assigned to the Stage/Group associated with this page, see <https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments> |
Run Bundler through the GitLab Dependency Firewall. (BETA)
Run the Bundler binary (bundle) through the GitLab Dependency Firewall. The command checks each package download and upload against the policy for the current project, refuses blocked packages, and summarizes the results after the run.
The command uses your package manager's registry or index configuration, and does not modify it.
When a bundle is already vendored, Bundler installs from vendor/bundle/ and the firewall does not check those packages. Clear that directory, or run bundle install --force, to check them again.
All arguments are forwarded to bundle verbatim.
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/.
glab dependency-firewall bundle <bundle args> [flags]
# Install dependencies through the Dependency Firewall
glab dependency-firewall bundle install
# Update dependencies through the Dependency Firewall
glab dependency-firewall bundle update
-h, --help Show help for this command.