3.1.0: Use a sandbox environment for Jinja

Potentially breaking change (with a low probability)

• Use a sandbox environment for Jinja (#202). Unless very very strange things are done in your vault-cli template jinja templates, this should not be breaking.

3.0.0: Removing `!template!`

Breaking changes

• Removing !template! (#198): See GHSA-q34h-97wf-8r8j

Changelog

• Remove Eric from codeowners (#201)

Kudos:

@elemoine

2.2.1: Fix deprecation warning

Changelog

• Use a logger warning otherwise it's not displayed properly. (#200)

2.2.0: Deprecate templated values

Breaking changes

Changelog

• Add deprecation warning for using !template! (#199)
• Add @elemoine to CODEOWNERS (#197)

Kudos:

@ewjoachim

2.1.0: Default umask to restrict permissions on file

Breaking changes

• Default umask to restrict permissions on file (#196). Use --umask, VAULT_CLI_UMASK or umask: in the config file to explicitely select a less restrictive umask if you need to.

2.0.0: Removed legacy command name `vault`

Breaking changes

Command name is now vault-cli only. Launching vault-cli with command vault doesn't work anymore.

Changelog

• Remove legacy name for cli tool (#194)

1.8.0: `vault-cli env --file` to write files with secrets to the disk before launching a command

Changelog

• Vault-env can write files (#186)

Kudos:

@sheb

1.7.0: vault-cli set-all, fix certificates

Breaking changes

Changelog

• Fix #191: Temporary avoid newer hvac releases for certificate issues (#192)
• Fix mypy (#193)
• Goodbye Mickaël - Remove @mgu from codeowners (#190)
• Refactor vault-cli env, rename --path to --envvar (with compat) (#189)
• vault-cli set-all (#188)
• CI on both PRs and the master branch (#183)

1.6.0: vault-cli cp

Changelog

• Added vault-cli cp (#181)
• Run CI on PRs based on forks (#182)

Kudos:

@soualid, congratulation for you first contribution to Vault-CLI

1.5.1: Fix automated release

Changelog

• Fix automated release (#180)