Command Line Options
Some command line options aren’t associated with a specific command, but can provided to any command instead.
Commodore creates a large amount of directories and files. By default, this happens in the current working directory of the environment in which Commodore is executed. If this option is provided, Commodore will create its directories and files in the provided location.
Show the version and exit.
- -v, --verbose
Control verbosity. Can be repeated for more verbose output. Can also be provided after subcommands (for example
commodore catalog compile -v).
Currently three verbosity levels are implemented, regular operation is active when the flag isn’t provided, debug verbosity is enabled when the flag is provided once or more, and trace verbosity is enabled when the flag is provided three times or more.
Show help message for generic options and available commands then exit.
- --api-url URL
Lieutenant API URL.
- --api-token TOKEN
Lieutenant API token.
Run in local mode. Intended to be used to test/verify local changes (for example during component development) against an existing cluster inventory and catalog.
Local mode doesn’t try to connect to the Lieutenant API or fetch/push Git repositories. However, local mode expects the working directory to contain a valid inventory in
inventory/and all the dependencies (components and Jsonnet libraries) required by the inventory in
dependencies/, with component classes symlinked to
inventory/and component and 3rd party Jsonnet libraries symlinked to
In local mode, uncommitted modifications to the inventory and dependencies are never discarded.
Local mode will fail when the cluster id of the inventory differs from the cluster id for which compilation was requested.
catalog/is provided for a local mode compilation, Commodore will show a diff of the changes compared to the provided catalog. There’s currently no mechanism that ensures that the provided cluster catalog actually matches the cluster for which compilation was requested.
The quickest way to get a working directory setup for local mode is to run a "regular"
catalog compilefor the cluster you want to work against.
See also local mode documentation.
Push catalog to remote repository as discovered in the cluster configuration fetched from the Lieutenant API.
Show changes and prompt if they should be pushed to the remote repository. This doesn’t do anything unless
- --git-author-name USERNAME
Name of catalog commit author
- --git-author-email EMAIL
E-mail address of catalog commit author
Show catalog clean usage and options then exit.
- -f, --values FILE
Specify inventory class in a YAML file. This option can be repeated to provide multiple files. Files specified later win when resolving inventory values.
- -J, --search-paths DIRECTORY
Specify additional search paths.
- -o, --output DIRECTORY
Specify output path for compiled component. Defaults to
Show catalog compile usage and options then exit.
- --name TEXT
The component’s name as it will be written in the documentation. Defaults to the slug.
- --lib / --no-lib
Add a component library template. Defaults to no.
- --pp / --no-pp
Add a component postprocessing template. Defaults to no.
- --owner TEXT
The GitHub user or project name where the component will be hosted. Defaults to projectsyn.
- --copyright TEXT
The copyright holder added to the license file. Defaults to "VSHN AG <firstname.lastname@example.org>".
Show component new usage and options then exit.