Latest release

v0.6.0

@dustinmm80 dustinmm80 released this Jun 20, 2016 · 6 commits to master since this release

  • Write temporary files to home directory if possible

This release addresses issue #32.

Downloads

v0.5.0

@dustinmm80 dustinmm80 released this Jun 8, 2016 · 12 commits to master since this release

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.

Downloads

v0.3.1

@dustinmm80 dustinmm80 released this Feb 3, 2016 · 36 commits to master since this release

  • Integer values set in secrets.yml are now parsed correctly GH-21

EDIT: binaries were cross-compiled incorrectly, this has been fixed in v0.3.2

Downloads

v0.3.0

@dustinmm80 dustinmm80 released this Aug 21, 2015 · 42 commits to master since this release

  • Install bash completions if available
  • Switch to tar.gz instead of .zip
  • Try to find provider in the default path if just a name given
  • Allow -p argument to override SUMMON_PROVIDER envar
  • Check if provider exists and is executable

Downloads