Releases: cyberark/summon
Releases · cyberark/summon
v0.6.7
v0.6.6
v0.6.5
v0.6.4
- Don't rely on executable bit on the provider (#41). Instead provide descriptive error if it fails to run. (Fixes issue #40.)
SHA256 sums:
28767f28ac6f4e33e5e2bad9f40d2989b51e04ef09c78c88cff28e3f03781481 summon_v0.6.4_darwin_amd64.tar.gz
0ec97b153b25ced36a883873d44ea1431b550fd1adbfe35f437f6abdd95781db summon_v0.6.4_linux_amd64.tar.gz
e2df4ec9254d4e84e15cac982a0605ae3d0165d17c2f06dac95adb75c060ddbd summon_v0.6.4_windows_amd64.tar.gz
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Added -e, --environment
flag - Specifies section (environment) to parse from secret YAML
This flag specifies which specific environment/section to parse from the secrets YAML file (or string). In addition, it will also enable the usage of a common section which will be inherited by other sections/environments. In other words, if your secrets.yaml looks something like this:
common:
DB_USER: db-user
DB_NAME: db-name
DB_HOST: db-host.example.com
staging:
DB_PASS: some_password
production:
DB_PASS: other_password
Doing something along the lines of: summon -f secrets.yaml -e staging printenv | grep DB_
, summon will populate DB_USER, DB_NAME, DB_HOST with values from common and set DB_PASS to some_password.
v0.4.0
- breaking change Default provider path is now
/usr/local/lib/summon
.