spruce-release Release v1.19.2

New features

Thanks to @HeavyWombat and @dargmuesli, we now have a docker image for spruce! It's
built for every master commit as the latest tag, with versioned release tags for each
official release of spruce (e.g. gfranks/spruce:v1.19.2)

Fixes

Bumped the version of go-patch being used in spruce, to resolve issues like #283, thanks
for catching this @andrew-edgar!

spruce-release Release v1.19.1

Bug Fixes

• Fixes #278 where --cherry-pick was not evaluating operators that did not depend on other operators

spruce-release Release v1.19.0

New Features

• (( load "FILENAME" )) has been added. The load operator will load the contents of a YAML file,
  into the datastructure where it was invoked. See the [docs|https://github.com/geofffranks/spruce/blob/master/doc/operators.md#-load-]
• (( vault ... )) now supports the KV v2 API if you set VAULT_VERSION=2 in your environment. By default, spruce
  will continue to use the v1 API (VAULT_VERSION=1)

Acknowledgements

Many thanks to @HeavyWombat for the load operator!
Great work from @yurinnick to add the Vault KV v2 API support!

spruce-release Release v1.18.2

Fixes

• The default behavior of merging lists of maps now matches the behavior of implicit merging, fixing #267

Acknowledgements

Thanks @HeavyWombat for the discovery + fix!

spruce-release Release v1.18.1

New Features

• A new (( sort )) operator has been added enable sorting in
  the post-processing of paths that point to lists of strings,
  lists of numbers, or lists of named-entry maps.

Acknowledgements

Thanks to @HeavyWombat for the new feature!

spruce-release Release v1.18.0

Improvements

• When running spruce json while there was a key of integer 4, and a key of the
  string "4", with two different values, spruce json will only allow one of them
  to win, as JSON only permits strings as keys, and one will invevitably overwrite
  the other. This will now emit a warning by default. Thanks @sorenh for adding this!
• spruce json now supports an optional --strict flag to prevent non-string keys
  from being converted into json at all. Another thank you to @sorenh!

Removals

• The long-deprecated --concourse flag has been removed from spruce. Please use
  either the (( grab )) operator, or Concourse's ((variable)) syntax for pulling
  in the credentials.

spruce-release Release v1.17.0

New Features

• The (( delete )) operator can now delete strings form simple lists of
  strings. For example:

  --- # this list
  array:
  - first
  - second
  - third
  --- when merged with this
  array:
  - (( delete second ))
  --- # yields
  array:
  - first
  - third
  

  Many thanks to @qu1queee and @HeavyWombat for the new feature!

• The (( vault )) operator now honors the HTTP_PROXY, HTTPS_PROXY, and
  NO_PROXY environment variables for using a proxy to connect to the Vault server.

  Thank you @drnic for the update!

spruce-release Release v1.16.2

Bug Fixes

Fixed a bug where spruce was pruning the wrong element in a list, if that list's
order had been modified via array operators like (( prepend )).

Acknowledgements

Many thanks @HeavyWombat for the fix!

spruce-release Release v1.16.1

#Bug Fixes

• spruce diff output used to be colorized based on whether or not STDERR was
  sent to a terminal. This led to issues piping or redirecting the actual diff output,
  so now the decision is based on what type of device STDOUT is. All other spruce
  subcommands are unaffected, and continue to colorize based on STDERR's device type.

  Thanks @giner for pointing this out!

spruce-release Release v1.16.0

Minor CI Improvements