f7217245a7
Currently airshipctl will overwrite an existing config file by default during config init execution. This patch adds an appropriate flag to explicitly control whether the user wants to overwrite an existing file or not. Change-Id: I9f4756b98e9d1245145809aed203974e99feb662 Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
1.7 KiB
1.7 KiB
airshipctl config
Manage the airshipctl config file
Synopsis
Manage the airshipctl config file
Options
-h, --help help for config
Options inherited from parent commands
--airshipconf string Path to file for airshipctl configuration. (default "$HOME/.airship/config")
--debug enable verbose output
SEE ALSO
- airshipctl - A unified entrypoint to various airship components
- airshipctl config get-context - Get context information from the airshipctl config
- airshipctl config get-encryption-config - Get an encryption config information from the airshipctl config
- airshipctl config get-management-config - View a management config or all management configs defined in the airshipctl config
- airshipctl config get-manifest - Get a manifest information from the airshipctl config
- airshipctl config init - Generate initial configuration file for airshipctl
- airshipctl config set-context - Manage contexts
- airshipctl config set-encryption-config - Manage encryption configs in airship config
- airshipctl config set-management-config - Modify an out-of-band management configuration
- airshipctl config set-manifest - Manage manifests in airship config
- airshipctl config use-context - Switch to a different context