ad7f80f2bf
Currently, if config file doesn't exist - airshipctl doesn't throw an error and uses empty config object instead. It seems this behavior was an attempt to hide an error if there was a call of subcommand which is not require proper config file. Since we moved config load calls to the specific subcommands from root level - current behavior should be changed and we have to throw an error instead if it's not possible to access config file. Change-Id: I7e949fbc9d48d682e26500e0b6b6b9bd12665e24 Relates-To: #199 Closes: #199 Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
Airshipctl
Airshipctl is a command-line interface that enables users to manage declarative infrastructure and software.
Airshipctl aims to provide a seamless experience for operators wishing to leverage the best open source options such as the Cluster API, Metal Kubed, Kustomize, and kubeadm by providing a straight forward and easily approachable interface.
This project is the heart of our effort to produce Airship 2.0, which has three main evolutions from Airship 1.0:
- Expand our use of entrenched upstream projects.
- Embrace Kubernetes Custom Resource Definitions (CRD) – everything becomes an object in Kubernetes.
- Make the Airship control plane ephemeral.
To learn more about the Airship 2.0 evolution, reference the Airship blog series.
Contributing
Airshipctl is under active development and welcomes new developers! Please read our developer guide to begin contributing.
We also encourage new contributors and operators alike to join us in our Slack workspace and subscribe to our mailing lists.
You can learn more about Airship on the Airship wiki.