vela config migrate
Adopt a legacy config into a Config CR.
Synopsis
Adopt a legacy config (a velacore-config Secret) into a Config CR of the same name. The template may already be a ConfigTemplate CR or still a legacy ConfigMap; both work, unless a ConfigTemplate that migration did not create shadows the legacy ConfigMap, which is a conflict. The Secret is kept and becomes owned by the Config; a second run skips it. --all does this for every legacy config in the namespace, with or without a template. Secrets a GitOps tool applies are adopted too and the report lists them: commit their new Configs to the repository the GitOps tool applies the Secrets from, or the tool reverts them.
vela config migrate [flags]
Examples
vela config migrate my-config -n my-team
vela config migrate my-config -n my-team --dry-run
vela config migrate --all -n my-team
Options
--all migrate every legacy config in the namespace
--dry-run print the CRs that would be created and the objects that would be adopted, and change nothing
-h, --help help for migrate
-n, --namespace string specify the namespace of the config (default "vela-system")
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 config - Manage the configs.