enable vault hardening
Merge request reports
Activity
- A deleted user
added botmr statusreview vault labels
assigned to @marcel.ehoussou
requested review from @ryan.j.garcia, @chris.oconnell, and @michaelmartin
changed milestone to %2.25.0
@marcel.ehoussou I think this is breaking on clean installs.
What I think is happening is prior to hardening, the keys get created correctly and the upgrade pipeline succeeds -- since the keys were already created.
The
Clean Install
pipelines are failing, since we are locked down at the start. Suspect we might need a custom service entry at the bigbang level to allow this to work on a clean install.Edited by Michael Martinadded statusdoing label and removed statusreview label
added 11 commits
- 883e69c6 - 1 earlier commit
- 535ddfc2 - addons
- 2c0bc9b8 - fix vault test values
- 379e2c94 - test
- caf266aa - Merge branch 'master' into test-whitelist-vault-75
- 20e7bf78 - update branch with master
- 3f305dc9 - new test values
- 3c419f9e - allow vault cypress test
- c44c6442 - Merge remote-tracking branch 'origin/master' into test-whitelist-vault-75
- 13f4dd15 - Merge branch 'test-whitelist-vault-75' into update-vault-tag-0.25.0-bb.21
- 31c97206 - merge bb test-values into vault tag
Toggle commit listadded 1 commit
- a0e3589a - Fix indentation for vault yaml, fix placement of vault values so they are under the vault key
added debug label
changed milestone to %2.26.0
Getting error:
vault vault-vault-0 1/2 CrashLoopBackOff 8 (2m46s ago) 19m
. AddedDebug
for more details on the crashLoopBack error but still investigating and running some tests.Edited by MARCEL EHOUSSOU