Support Vault to OpenBao migration#2095
Conversation
There was a problem hiding this comment.
Code Review
The pull request introduces a comprehensive set of Ansible playbooks and updated documentation to support the migration from Hashicorp Vault to OpenBao. The new playbooks are well-structured to manage the migration process across seed and overcloud environments, including configuration updates. However, a critical issue exists in the migration playbooks where the stackhpc_ca_secret_store variable is used dynamically to include secret store keys. This can lead to incorrect key retrieval if the variable is already set to 'openbao' during a Vault migration, causing the migration to fail. Additionally, there are minor documentation formatting issues and some file permissions that could be more restrictive for sensitive configuration files.
3cc8df4 to
69ec42b
Compare
|
Linters are failing because missing playbook is not released from stackhpc.hashicorp collection yet |
69ec42b to
314b1e1
Compare
a211eaa to
3eac2af
Compare
9fe21f3 to
8a5dde7
Compare
2794b86 to
7e9d23e
Compare
5817b25 to
58baa30
Compare
Co-Authored-by: Alex Welsh <alex@stackhpc.com>
This brings Vault to OpenBao migration support
58baa30 to
2bbafe6
Compare
Adds four playbooks used for migrating Vault to OpenBao.
The version of
stackhpc.hashicorpcollection needs to be bumped after stackhpc/ansible-collection-hashicorp#85 is merged and released.But as SKC's contents are ready, marked as ready.