Ed,
The actions are still trivial to automate. They could be run in bash or here is an example we use for CI/CD in our testing with python [0].
The critical point is that the vault certificates setup happen after the deploy has settled.
The bug, which we still intend to fix but at a lower priority, is that during deploy time changing from http to https is a race condition nightmare.
[0] https://github.com/openstack-charmers/zaza/blob/master/zaza/charm_tests/vault/setup.py#L57
Ed,
The actions are still trivial to automate. They could be run in bash or here is an example we use for CI/CD in our testing with python [0].
The critical point is that the vault certificates setup happen after the deploy has settled.
The bug, which we still intend to fix but at a lower priority, is that during deploy time changing from http to https is a race condition nightmare.
[0] https:/ /github. com/openstack- charmers/ zaza/blob/ master/ zaza/charm_ tests/vault/ setup.py# L57