mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-17 03:57:01 +02:00
Sometimes destroying resources in AWS will fail because of unexpected dependency violations or other such nonsense. When this happens the behavior of Vault that we wanted to verify has already been successfully accomplished, however the required workflow will fail. This change allows us to succeed if `enos scenario launch` completes but allows `enos scenario destroy` to fail. We still notify our slack channel on destroy failures so that we can investigate issues, however it won't require a PR author to retry. * Execute `enos scenario launch` instead of `enos scenario run` to allow for very occasional issues when tearing down test infrastructure. * Improve an error message when getting secondary cluster IP addresses. * Don't race to get secondary cluster IP addresses. * Add secondary token to replication scenario outputs. Signed-off-by: Ryan Cragun <me@ryan.ec> |
||
---|---|---|
.. | ||
scripts | ||
main.tf |