Skip to content

Releases: cyberark/summon

v0.6.7

06 Aug 20:19
Compare
Choose a tag to compare

Added

  • deb and rpm packages

Changed

v0.6.6

06 Feb 16:58
1973af0
Compare
Choose a tag to compare
  • Removed the buffer that captured stdout when running the subprocess that summon wraps. #64

This bugfix will greatly reduce the memory usage of summon when wrapping long-lived processes the generate standard output.

v0.6.5

23 Aug 12:49
ccba7f0
Compare
Choose a tag to compare

#v0.6.5

  • Minor release, no functionality changes
    • Improved Jenkins CI pipeline.
    • Binaries are now built for more distributions (see PLATFORMS in build.sh).
    • Simpler docker-compose development environment.

v0.6.4

12 Apr 19:35
v0.6.4
Compare
Choose a tag to compare
  • 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

13 Mar 14:16
98591b2
Compare
Choose a tag to compare
  • Summon now passes the child exit status to the caller - PR #39

v0.6.2

23 Jan 16:36
7fa8318
Compare
Choose a tag to compare
  • Added 'default' section support, this is an alias for 'common' - PR #37

v0.6.1

19 Dec 23:41
Compare
Choose a tag to compare

Bugfix release:

  • Booleans literals are now handled properly - #35

v0.6.0

20 Jun 19:54
Compare
Choose a tag to compare
  • Write temporary files to home directory if possible

This release addresses issue #32.

v0.5.0

08 Jun 16:02
Compare
Choose a tag to compare

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

01 Mar 20:27
Compare
Choose a tag to compare
  • breaking change Default provider path is now /usr/local/lib/summon.