Mick McGrath

helm copy default before and after scripts

5

https://github.com/bitovi/bitops/blob/master/scripts/helm/copy-defaults.sh should copy `default/helm//bitops.before-deploy.d` and `default/helm//bitops.after-deploy.d`

We're currently using circleci with a paid plan for building bitops images. We should consider either [CircleCI credits](https://circleci.com/docs/2.0/credits/) or github actions

create a composite action which encapsulates the `deploy.sh` script

Currently, terraform only copies `_default/terraform/values`. This should be extended to handle arbitrary things like `_default/terraform/modules/*` etc. - file: https://github.com/bitovi/bitops/blob/master/scripts/terraform/copy_defaults.sh - reference in tf deploy.sh: https://github.com/bitovi/bitops/blob/master/scripts/terraform/deploy.sh#L31

[this](https://github.com/bitovi/bitops/blob/master/scripts/helm/helm_handle_chart.sh#L36-L65) is confusing

Since lot of AWS customers use EKSCTL for AWS EKS cluster creation, Bitops should provide support for EKSCTL api as it will be a value addition.

Add `istioctl` support Ops repo environments should be able to specify: ``` operations/ - env1/ - istio/ - bitops.config.yaml - profiles/ #

Secrets management

6

- Examples in docs (before scritps, etc) - external secrets manager support (vault, etc) - pluggable if possible - encrypt in place patterns (helm secrets, [sops](https://github.com/mozilla/sops), etc)

Multiple Operations On the Same Bitops environment

1

from @ConnorGraham --- **Background** I have a use-case where my ansible playbook handles different operations (`beta-create`, `beta-promote`, `beta-destroy`), depending on the lifecycle of a single CI build. This is handled...

# Problem https://garden.io/ allows you to codify a complete description of your stack, including how it's built, deployed and tested, using the Stack Graph—making your workflows reproducible and portable. It...