update in configuration of manifest repos in airshipctl
Hello, What is the format of the command to update the configuration related to manifest repos in airshipctl? Use cases: (1) user/operator wants to change the repo from treasuremap to a private repo (2) user / operator wants to add a repo for security documents. There is one option --manifest that is available set-context sub-command, which set a manifest object to the config. However it is not very obvious from help how new manifest object and its configuration like url, credentials to access repo can be appended / updated. root@ubuntu:~/airshipctl# ./bin/airshipctl config set-context -h Sets a context entry in arshipctl config. Specifying a name that already exists will merge new fields on top of existing values for those fields. Usage: airshipctl config set-context NAME [flags] Examples: # Create a completely new e2e context entry airshipctl config set-context e2e --namespace=kube-system --manifest=manifest --user=auth-info --cluster-type=target # Update the current-context to e2e airshipctl config set-context e2e # Update attributes of the current-context airshipctl config set-context --current --manifest=manifest Flags: --cluster string sets the cluster for the specified context in the airshipctl config --cluster-type string sets the cluster-type for the specified context in the airshipctl config --current use current context from airshipctl config -h, --help help for set-context --manifest string sets the manifest for the specified context in the airshipctl config --namespace string sets the namespace for the specified context in the airshipctl config --user string sets the user for the specified context in the airshipctl config Global Flags: --airshipconf string Path to file for airshipctl configuration. (default "$HOME/.airship/config") --debug enable verbose output --kubeconfig string Path to kubeconfig associated with airshipctl configuration. (default "$HOME/.airship/kubeconfig") It does not seem to be right output. Instead of printing the help it is actually processing the command inputs root@annie:~/airshipctl# ./bin/airshipctl config set-context --manifest -h you must specify a non-empty context name root@annie:~/airshipctl# ./bin/airshipctl config set-context --manifest --help you must specify a non-empty context name root@annie:~/airshipctl# ./bin/airshipctl config set-context default --manifest --help context "default" modified. Regards, Aniruddha
Hello Aniruddha!
What is the format of the command to update the configuration related to manifest repos in airshipctl?
The preferred way of updating your airshipctl config file is by modifying the configuration file directly; however, we have added capabilities to change some options on an "as-needed" basis using command-line arguments and flags. For example, you can use the command-line to switch between pre-defined contexts in your configuration file and modify which manifests, module configurations, etc a context uses. As far as I am aware, this functionality has not been extended to manifest configuration, and I am not sure that it is planned. I encourage you to file a feature request on our GitHub issues page [0]. Each new issue is reviewed during our weekly flightplan call [1], and the issue could even be assigned that day if the functionality is desired. In the meantime, I recommend updating manifest data in the configuration file.
(1) user/operator wants to change the repo from treasuremap to a private repo
Each manifest holds multiple repositories [2]. Therefore, if your active context references a manifest with multiple repositories, all of those repositories will be cloned. There is no need to identify which repository you would like to use; identify which set of repositories (the manifest) you would like to use.
It does not seem to be right output. Instead of printing the help it is actually processing the command inputs
I agree; we should print the help menu options whenever -h or --help is passed, even if using a sub-command. I have filed an issue to track this [3]. Best regards, Drew Walters [0] https://github.com/airshipit/airshipctl/issues [1] https://wiki.openstack.org/wiki/Airship#AIRSHIP_Flight_Plan_-_Community_Mana... [2] https://github.com/airshipit/airshipctl/blob/master/pkg/config/utils.go#L37 [3] https://github.com/airshipit/airshipctl/issues/114
Thanks Drew... Appreciate your response! Regards, Aniruddha -----Original Message----- From: WALTERS, ANDREW <aw442m@att.com> Sent: Monday, March 16, 2020 7:22 AM To: GAUTAM, ANIRUDDHA SINGH <ag878f@att.com>; airship-discuss@lists.airshipit.org Subject: RE: [Airship-discuss] update in configuration of manifest repos in airshipctl Hello Aniruddha!
What is the format of the command to update the configuration related to manifest repos in airshipctl?
The preferred way of updating your airshipctl config file is by modifying the configuration file directly; however, we have added capabilities to change some options on an "as-needed" basis using command-line arguments and flags. For example, you can use the command-line to switch between pre-defined contexts in your configuration file and modify which manifests, module configurations, etc a context uses. As far as I am aware, this functionality has not been extended to manifest configuration, and I am not sure that it is planned. I encourage you to file a feature request on our GitHub issues page [0]. Each new issue is reviewed during our weekly flightplan call [1], and the issue could even be assigned that day if the functionality is desired. In the meantime, I recommend updating manifest data in the configuration file.
(1) user/operator wants to change the repo from treasuremap to a private repo
Each manifest holds multiple repositories [2]. Therefore, if your active context references a manifest with multiple repositories, all of those repositories will be cloned. There is no need to identify which repository you would like to use; identify which set of repositories (the manifest) you would like to use.
It does not seem to be right output. Instead of printing the help it is actually processing the command inputs
I agree; we should print the help menu options whenever -h or --help is passed, even if using a sub-command. I have filed an issue to track this [3]. Best regards, Drew Walters [0] https://github.com/airshipit/airshipctl/issues [1] https://wiki.openstack.org/wiki/Airship#AIRSHIP_Flight_Plan_-_Community_Mana... [2] https://github.com/airshipit/airshipctl/blob/master/pkg/config/utils.go#L37 [3] https://github.com/airshipit/airshipctl/issues/114
participants (2)
-
GAUTAM, ANIRUDDHA SINGH
-
WALTERS, ANDREW