A CLI for managing declarative infrastructure.
Go to file
Sean Eagan 9097b38f80 Improve release notes issue selection accuracy
The existing behavior was to select issues closed between two tag
dates. This is error prone since issues may be closed after the
fact, and there may be multiple releases being worked at the same
time and it is impossible to tell which release an issue was
closed for.

This switches to selecting issues by matching their milestone name
against the git tag. Since github does not support assigning
multiple assignments, their will likely need to be some manual
issue additions to the release notes when an issue is targeted to
multiple releases e.g. v2.0.1 and v2.1.

This also moves to only triggering github release creation on
non-pre-release semver tags, to avoid cluttering the release
list.

Change-Id: I99824020789323f8a1db418c73acef57ebb86022
Signed-off-by: Sean Eagan <seaneagan1@gmail.com>
2021-04-22 13:24:43 -05:00
.github Improve release notes issue selection accuracy 2021-04-22 13:24:43 -05:00
certs Adding the ability to inject certificate authorities into docker image 2020-04-24 15:06:11 -05:00
cmd Merge "Change logic of config set-management-config command" 2021-03-31 12:02:34 +00:00
docs Added script for the missing controlplane_target phase 2021-04-13 10:47:47 -07:00
krm-functions Merge "Use env variables only for exec process in KRM toolbox" 2021-04-20 16:56:48 +00:00
manifests Add set -xe to deployment shell phase-helpers 2021-04-21 18:31:47 +04:00
pkg Merge "Do not pass phase helper to executor initializers" 2021-04-20 17:40:58 +00:00
playbooks Merge "Disable the redundant github issue update job" 2021-04-21 01:31:37 +00:00
roles Use Zuul project variable for build images 2021-04-15 21:26:41 +00:00
testdata/k8s Remove NameInKubeconf field from Context struct 2021-03-26 19:22:52 -05:00
tests/ansible Reusing apache-server instead of httpd 2020-05-01 03:17:02 +00:00
testutil Do not pass phase helper to executor initializers 2021-04-20 10:00:47 +03:00
tools Deployment script enhancements 2021-04-20 18:48:35 +00:00
zuul.d Merge "Disable the redundant github issue update job" 2021-04-21 01:31:37 +00:00
.gitignore Fix typo in .gitignore 2020-05-20 16:07:49 -05:00
.gitreview Gerrit: Add .gitreview file 2019-06-25 08:11:57 -05:00
.golangci.yaml Replace Non-ASCII symbols 2020-08-05 13:22:59 +00:00
.goreleaser.yaml Publish binaries on release 2021-02-09 14:25:38 +00:00
.grenrc.js Github action to create release notes 2020-11-13 15:11:06 -06:00
CONTRIBUTING.md Guideline against very large Gerrit Changes 2020-07-06 20:51:00 +05:00
Dockerfile Update base Go builder image to 1.15 2021-04-08 22:18:18 +02:00
go.mod Fix docker stdin write. 2021-04-07 14:37:17 +00:00
go.sum Fix docker stdin write. 2021-04-07 14:37:17 +00:00
LICENSE Add LICENSE 2019-10-19 14:16:05 -05:00
main.go Refactor airshipctl root command 2020-08-25 17:37:19 -05:00
Makefile Add base images override support 2021-04-12 19:47:31 +02:00
README.rst Airship blog series link fix 2020-10-14 21:08:35 +00:00
tox.ini Replace venv with tox for documentation builds 2020-05-08 15:47:41 +00:00
Vagrantfile [#32]: scripts for local run playbooks 2020-02-28 17:24:32 -08:00

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.