79555848f2
TestPull unit test should not perform functional verification. The purpose of cmd unit tests should be testing proper cmd object creation, not actually run the command. Moreover, we don't have possibility to mock and track all the objects that created inside of called functions. We can only verify golden output with help or when command performs basic stuff just inside of RunE interface. Actual test of called methods performed in pkg module. Change-Id: I2ad6b76f67cbf59d798c0f2b93752b3e3b3b053d Signed-off-by: Ruslan Aliev <raliev@mirantis.com> |
||
---|---|---|
.github | ||
certs | ||
cmd | ||
docs | ||
manifests | ||
pkg | ||
playbooks | ||
roles | ||
testdata/k8s | ||
tests/ansible | ||
testutil | ||
tools | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
.golangci.yaml | ||
CONTRIBUTING.md | ||
Dockerfile | ||
go.mod | ||
go.sum | ||
LICENSE | ||
main.go | ||
Makefile | ||
README.rst | ||
tox.ini | ||
Vagrantfile |
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.