Skip to content

Avoid eager vault lookup for YAML secrets#2172

Draft
ideaship wants to merge 1 commit intomainfrom
rl_graceful_non-vault_deployment
Draft

Avoid eager vault lookup for YAML secrets#2172
ideaship wants to merge 1 commit intomainfrom
rl_graceful_non-vault_deployment

Conversation

@ideaship
Copy link
Copy Markdown

@ideaship ideaship commented Apr 8, 2026

Add load_yaml_file and reuse it in the CLI paths that read OpenStack, RabbitMQ, Octavia, and database secrets from YAML files.

Several commands called get_vault() before checking whether the file was actually vault-encrypted. In deployments that keep secrets as plain YAML, this produced repeated 'Unable to get ansible vault password' errors for a path that is never needed.

Read the file first and only initialize the vault when the content is encrypted. This removes noisy false-error output during checks and deployments while preserving decryption for encrypted secrets.

AI-assisted: Codex

Add load_yaml_file and reuse it in the CLI paths that read
OpenStack, RabbitMQ, Octavia, and database secrets from YAML files.

Several commands called get_vault() before checking whether the file
was actually vault-encrypted. In deployments that keep secrets as
plain YAML, this produced repeated 'Unable to get ansible vault
password' errors for a path that is never needed.

Read the file first and only initialize the vault when the content is
encrypted. This removes noisy false-error output during checks and
deployments while preserving decryption for encrypted secrets.

AI-assisted: Codex
Signed-off-by: Roger Luethi <luethi@osism.tech>
@ideaship ideaship force-pushed the rl_graceful_non-vault_deployment branch from 9b64454 to 61417df Compare April 8, 2026 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant