v0.5.0

Changelog

Features

• #10 makes the current vault token available as a secret at path mycro.secrets('vault.token')

v0.4.0

Changelog

Breaking Changes

• #8 complete refactor in how this hook functions. more detail outlined below:

  This hook is now much more opinionated. We now require secret configurations to be stored in DynamoDB. This now allows this hook to operate without environment variables, instead relying on EC2 instance profiles. The config for the hook is now reduced to basic instructions for retrieving the proper config object from DynamoDB, and then using the config to contact vault. See updated README.md for more info

v0.3.2

Changelog

Bugfixes

• #7 fixes issue with bad url building logic

v0.3.1

Changelog

Bugfixes

• #7 fixes bad url building logic ( issue #6 )

v0.3.0

Changelog

Features

• #5 adds support for additional headers applied to vault requests ( closes #4 )

v0.2.1

Changelog

Bugfixes

• #3 fixes issue with secrets config throwing validation error for optional key logValidationErrors ( #2 )

v0.2.0

Changelog

Features

• #1 updates the env key api to follow suite with the vault key api
• #1 updates README