armada/armada
Sean Eagan c75898cd6a Airship 2 support features
Airship 2 is using Argo for workflow management, rather
than the builtin Armada workflow functionality. Hence, this
adds an apply_chart CLI command to apply a single chart at
a time, so that Argo can manage the higher level orchestration.

Airship 2 is also using kubernetes as opposed to Deckhand as the
document store. Hence this adds an ArmadaChart kubernetes CRD,
which can be consumed by the apply_chart CLI command. The chart
`dependencies` feature is intentionally not supported by the CRD,
as there are additional complexities to make that work, and ideally
this feature should be deprecated as charts should be building in
there dependencies before consumption by Armada.

Functional tests are included to excercise these features
against a minikube cluster.

Change-Id: I2bbed83d6d80091322a7e60b918a534188467239
2020-03-25 13:56:32 -05:00
..
api api: Remove dry-run parameter 2019-09-05 16:29:04 +00:00
cli Airship 2 support features 2020-03-25 13:56:32 -05:00
common Standardize Armada code with YAPF 2019-07-31 10:16:15 -05:00
conf Standardize Armada code with YAPF 2019-07-31 10:16:15 -05:00
exceptions Standardize Armada code with YAPF 2019-07-31 10:16:15 -05:00
handlers Airship 2 support features 2020-03-25 13:56:32 -05:00
schemas Support builtin chart dependencies 2019-08-22 08:13:03 -05:00
tests Airship 2 support features 2020-03-25 13:56:32 -05:00
utils Allow proxy_server use for chart tarball downloads 2019-09-17 14:56:08 -07:00
__init__.py fix(init): remove duplicated version code 2018-05-28 05:52:58 -05:00
const.py Introduce v2 docs 2019-04-16 10:15:21 -05:00
shell.py Airship 2 support features 2020-03-25 13:56:32 -05:00
version.py Fix(linting): Make Armada pep8 compliant 2017-09-29 11:46:58 -04:00