1df0e74d12
`airshipctl document pull` does not yet support pull from git refs, and so cannot pull airshipctl patchsets to test their manifests. As a workaround, this change copies the airshipctl project directory that is used to build the binary / run the scripts (which can be set to a patchset via $MANIFEST_REPO_REF) to the expected /tmp location for serving manifests from patchsets as well. Support for testing treasuremap manifest patchsets is still unsupported. Change-Id: Ia9ec248efa2a12728e9eb6d3753b35ec5bae0d47 |
||
---|---|---|
.github | ||
certs | ||
cmd | ||
docs | ||
krm-functions | ||
manifests | ||
pkg | ||
playbooks | ||
roles | ||
testdata/k8s | ||
tests/ansible | ||
testutil | ||
tools | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
.golangci.yaml | ||
.goreleaser.yaml | ||
.grenrc.js | ||
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.