3ad8f34e3f
Neither ARG or ENV are not expandable in ENTRYPOINT, though since ENV is available at runtime, we can use it as a work-around here. Thus, before [0], ENTRYPOINT could be overridden using env by passing --env BINARY=../../../<path to any binary>. Now previous default behavior is broken since we don't have ENTRYPOINT env var. This commit fixes default behavior and allows to modify it from build arg as was intended with [0]. [0] https://review.opendev.org/c/airship/airshipctl/+/791886 Change-Id: I115df039bc4f845d07f53f68fa3b716d86e8b3a9 Signed-off-by: Andrii Ostapenko <andrii.ostapenko@att.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.