The command "airshipctl config get-context" will display the name of the contexts as well as the current context name.
Relates-To: #475
Change-Id: I8234d74f6b98869e27e4974a54b68230d8be8565
The description and examples are updated for the airshipctl
commands, which will be inturn used for generating documentation.
Please ignore the .md file changes in this PS. They are added for zuul
gates to pass. Here is the PS with generated documention
files https://review.opendev.org/c/airship/airshipctl/+/789250
Relates-To: #280
Change-Id: I7c088528842ff859f502d4484ff9a3847ebb1177
The description and examples are updated for the airshipctl
commands, which will be inturn used for generating documentation.
Please ignore the .md file changes in this PS. They are added for zuul
gates to pass. Here is the PS with generated documention
files https://review.opendev.org/c/airship/airshipctl/+/789250
Relates-To: #280
Change-Id: I323fa145b512e58cb878b117656c51bc39e76360
Now the target path for the default manifest is
$HOME/.airship/default. This is reasonable default
location.
The target path is a mandatory field in the
definition of a manifest. If a user wants
to use her current working directory as a location
the manifests, then it must be properly configured
in the $HOME/.airship/config.
Relates-To: #416
Relates-To: #417
Change-Id: I96601803939df5c7369d1580842dfabeb19aa017
Added yaml output flag to show plan list in yaml format
Relates-To: #394
Co-authored By: Niharika Bhavaraju<niha.twinkle@gmail.com>
Change-Id: I8bed077573eb79783cfc77e4ebf82c819f41d125
This commit addresses the bug that user is unable to see retrieved
manifest name or names, also simplifies the internal logic and
reorganizes unit tests.
Change-Id: I89bac0af811f744c209be2aee921033a5e8a4fca
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
Closes: #505
* command internal logic was revised and optimized
* added ability to delete/reset management config fields
* unit tests were reorganized, new cases were added
Change-Id: I911df180e6986cb1f4dab6aea01216c8a4e15353
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
Relates-To: #348
This patch implements CLI command to invoke plan validation.
Appropriate functionality was already added to pkg previously.
Change-Id: I038b49c8de0af65f38b62950b27b31d95a6301a9
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
Relates-To: #19
Relates-To: #497
Closes: #497
* command internal logic was revised and optimized
* added ability to delete/reset context fields
* unit tests were reorganized, new cases were added
Change-Id: Ie35d11405e88fea21abf33cb75f44b03bb4644fd
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
Relates-To: #348
Since this field is no longer actually used, there is need to
remove it completely.
Change-Id: I9f7002f8def31d1660919bd0128707e43a57ad71
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
There are some debries left after removing --kubeconfig flag
from support, this patch cleans them up.
Change-Id: Iabdd6bcbc59d169bf162c9cddb3cb264fb88a3f7
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
This change fixes a bug where the default values that are
populated during an `airshipctl config init` were getting
mixed in with user specified values at runtime. For example,
a user with two contexts defined in their airship config
file would actually see a third phantom context with default
values in the output of `airshipctl config get-context`.
Also fixes a number of the config cmd and pkg unit tests that
were affected by this bug.
Change-Id: Iac591d4c2a616090028eb730576478edefb82544
Closes: #447
Now if we run `airshipctl cluster get-kubeconfig` without args
it will return kubeconfig for the entire site, which will have
contexts for every cluster defined in cluster map.
Relates-To: #460
Closes: #460
Change-Id: Icf1f09724a5c60ac520b1dbcbda69c3280ac4c7e
It is not used anywhere anymore as commands themselves were
deprecated and removed in favor of clusterctl move and init
executors.
Change-Id: I526f75d95b70754034f0846edfc9d3e468648ced
Change ClusterMap API object to support multiple kubeconfig sources
for a cluster. If one kubeconfig source fails, kubeconfig builder
will not fail and move on to the next one. This behaviour will allow
to support cases when ephemeral cluster is not accesible anymore or
when target cluster is not yet accessible.
For more information please read issue #460 in airshipctl github
Relates-To: #460
Related-To: #460
Change-Id: I7cd32f78cd7c4ad8814eac357424c24216f40d76
This reverts commit 694067492cfedd5e7b369b396bfce9923c0ca3a1.
Reason for revert: Encryption configs inside airship config are
no longer required. Encrypt feature was implemented different way.
Change-Id: I1c8feec75000402e314e815e4832ce740f0e1254
Modified the test framework so that error messages are actualy checked
for an expected value (instead of previously only checking if there was
an error returned)
Closes-Bug: #451
Change-Id: I9c4b172a705a7648467afe41346c389c503e764b
We use phases for building the ephemeral ISO image, so
a user can use `phase run` command instead. It is better
to remove `image build` subcommand to avoid support of
an unnecessary piece of code.
Change-Id: Ife9b5fdebc3cdfd5dac3ecccc8fef55811741ce8
Closes: #473
This PS will allow us to retrieve kubeconfig from different
kind of sources.
Change-Id: I31381cf466c58373efda40d06587e34bef411c68
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
With this change we will be sure that no commands against bmh
hosts will be applied without selector flags specified, now if you
want to target all hosts in inventory you must specify --all flag
Relates-To: #364
Related-To: #364
Closes: #364
Change-Id: I0d615ea226528162e07acc96fa61b26e031145aa
