Problem
Currently users must manually create ansible/vault-password.txt by copying the password from the "Ansible ms Vault Password" Bitwarden entry, as documented in ansible/README.md.
This adds friction to the DevSpaces workflow and requires manual secret management.
Proposed Solution
Auto-mount the vault password file in DevSpaces workspaces using one of these approaches:
-
External Secrets Operator (if available in ocp-gpu cluster):
- Create ExternalSecret to sync from Bitwarden
- Mount as file in DevSpaces pods via devfile
-
Bitwarden CLI in postStart:
- Use existing bitwarden-cli integration
- Fetch secret and write to
ansible/vault-password.txt in postStart command
-
DevSpaces Secret Mount:
- Store as Kubernetes secret in openshift-devspaces namespace
- Mount via devfile volumes
Expected Outcome
ansible/vault-password.txt automatically available in DevSpaces workspaces
- No manual password copy step required
- Update ansible/README.md to remove manual instruction
References
Problem
Currently users must manually create
ansible/vault-password.txtby copying the password from the "Ansible ms Vault Password" Bitwarden entry, as documented inansible/README.md.This adds friction to the DevSpaces workflow and requires manual secret management.
Proposed Solution
Auto-mount the vault password file in DevSpaces workspaces using one of these approaches:
External Secrets Operator (if available in ocp-gpu cluster):
Bitwarden CLI in postStart:
ansible/vault-password.txtin postStart commandDevSpaces Secret Mount:
Expected Outcome
ansible/vault-password.txtautomatically available in DevSpaces workspacesReferences