vela module publish
Publish a module to an OCI or ECR registry.
Synopsis
Validate a module source tree and publish it as an OCI artifact tagged from its own version. A published version is immutable: change the module, bump version in _module.cue, publish again.
vela module publish <dir> [oci-ref] [flags]
Examples
Publish to the configured default registry:
vela module publish ./modules/s3
Publish to a named registry:
vela module publish ./modules/s3 --registry ecr
Publish straight to an ECR repository prefix:
vela module publish ./modules/s3 123456789012.dkr.ecr.us-west-2.amazonaws.com/modules
Check the target and the annotations without pushing:
vela module publish ./modules/s3 --registry ecr --dry-run
Republish a release candidate over itself while iterating:
vela module publish ./modules/s3 --registry ecr --version 1.1.0-rc1 --force
Options
--dry-run Print the target reference, tag, and annotations without pushing.
--force Overwrite an already-published version.
-h, --help help for publish
--password string Registry password. Empty uses the docker credential chain.
--password-stdin Read the registry password from stdin.
--registry string The configured module registry to publish to. Empty means the configured default.
--username string Registry username. Empty uses the docker credential chain.
--version string Override the artifact tag. Must be semver, and does not bypass version immutability. The module's own version in _module.cue is unchanged inside the artifact.
Options inherited from parent commands
-V, --verbosity Level number for the log level verbosity
-y, --yes Assume yes for all user prompts
SEE ALSO
- vela module - Manage KubeVela modules.