Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of [QT-616] Add seal_ha enos scenario into release/1.14.x #23869

Merged

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #23812 to be assessed for backporting due to the inclusion of the label backport/1.14.x.

The below text is copied from the body of the original PR.


Add support for testing Vault Enterprise with HA seal support by adding a new seal_ha scenario that configures more than one seal type for a Vault cluster. We also extend existing scenarios to support testing with or without the Seal HA code path enabled.

  • Extract starting vault into a separate enos module to allow for better handling of complex clusters that need to be started more than once.
  • Extract seal key creation into a separate module and provide it to target modules. This allows us to create more than one seal key and associate it with instances. This also allows us to forego creating keys when using shamir seals.
  • QT-615 Add support for configuring more that one seal type to vault_cluster module.
  • QT-616 Add seal_ha scenario
  • QT-625 Add seal_ha_beta variant to existing scenarios to test with both code paths.
  • Unpin action-setup-terraform

Overview of commits

@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Oct 26, 2023
@github-actions
Copy link

Build Results:
All builds succeeded! ✅

@ryancragun ryancragun merged commit c948c64 into release/1.14.x Oct 26, 2023
@ryancragun ryancragun deleted the backport/ryan/qt-616/cheaply-causal-jawfish branch October 26, 2023 21:36
@github-actions
Copy link

CI Results:
All Go tests succeeded! ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-changelog pr/no-milestone
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants