- Docs
- Build a Catalogue
- Package and publish
- Set enterprise defaults
Set enterprise defaults
Point every install at your organization's catalogue with no per-machine setup.
Add your catalogue’s location to catalogue.toml, and installs from your own agentbundle build use it by default.
Record the coordinates
Section titled “Record the coordinates”Add the location of your catalogue to catalogue.toml, the file that describes the catalogue:
[distribution.agentbundle.artifactory]enabled = truebase-url = "https://artifactory.example.test/artifactory"repository = "agentbundle-catalogues"bundle = "platform"channel = "stable"All five fields are required when enabled = true, and base-url must use HTTPS. Never put a password, token, or authenticated URL in this file.
Generate the defaults
Section titled “Generate the defaults”Write install-defaults.toml from those coordinates:
agentbundle catalogue sync-defaults --root . --writeThe generated file holds only the same non-secret coordinates. Run it again with --check in CI to catch drift.
Ship them in your wheel
Section titled “Ship them in your wheel”Commit install-defaults.toml beside catalogue.toml, then build and publish your organization wheel, the installable Python package. An installed copy builds its source from your coordinates:
catalogue+<base-url>/<repository>/catalogues/<bundle>/channels/<channel>.jsonSigning in to read the catalogue is separate, and Host on Artifactory covers it.
Install from the default
Section titled “Install from the default”With no catalogue argument, an install uses your default:
agentbundle install --pack coreIf it reaches the wrong catalogue, a personal source is set. Run agentbundle config unset source to let your default take over.
Next, host the catalogue on Artifactory, or see the full Artifactory distribution reference for CI, troubleshooting, and proxy settings.