Export a Crunu environment to Ansible Vault

What Crunu does with Ansible Vault

Crunu can export an environment to a keys.vault.yml file in the Ansible Vault 1.1 format, encrypted with AES256. Ansible's own tools open it with the password the Export dialog generates, with no Crunu software involved.

ansible-vault view keys.vault.yml

Use it when a playbook or a teammate's workflow already expects Ansible Vault, or as a copy of one environment you can open anywhere Ansible runs.

Export an environment

1. Open the environment and choose Export….
2. Pick Ansible Vault (keys.vault.yml).
3. Copy the generated password, keep it somewhere safe and download the file.

The export takes the files of the saved version you see when you open the dialog. Inside the vault is a YAML document that lists each file by its path, relative to the home directory, with its contents and whether it loads as environment variables.

What isn't supported

• Importing arbitrary Ansible Vault files. Crunu doesn't read a vault file made by Ansible. To bring values in, drag the decrypted files into an environment instead.
• Environments restricted by network. An environment with a network policy can't be exported to a file, because the file would carry its contents outside the allowed networks. This guards against accidents, not against someone who can already see the values.
• Keeping the file in sync. The export is a snapshot. A new version in Crunu needs a new export.

Other export formats

The same Export dialog offers an environment's variables as a single .env, an environment file with its own password, and an offline copy of every environment you can read, which opens with your password and Secret Key without the server.

Related

• Vault features
• Export and offline copy
• AWS credentials files