Genesis v2.7.9 Release Notes
Release Date: 2020-06-23 // almost 4 years ago-
๐ Improvements
โ Add new secret type of UUID
0๏ธโฃ In kit.yml, you can now generate UUIDs of all types. By default, you just
need to specify the type 'uuid' for a path and key (similar to how 'random'
works. The full syntax is:๐
uuid [v1|time|v3|md5|v4|random|v5|sha1] [namespace (<UUID>|dns|url|oid|x500)] [name <string>] [fixed]
With no arguments, a v4/random UUID is generated. If v3/md5 or v5/sha1 is
๐ specified, it takes a name and optional namespace argument to build the
hash, which will always generate the same value for the same input
arguments, unlike the other versions. The name can be any string, and the
namespace can be the pre-defined namespaces of dns, url, oid or x500, or any
arbitrary UUID string.๐ Expanded config support. Kits can now specify which configs are required
and for what hook scripts. This allows for custom cloud and runtime configs
to be validated and used for information. Furthermore, cloud config can now
be used during thenew
script to check if the required keys are present or
even propose values that can be added.๐ This is done using one of the following two styles:
--- # kit.yml required_configs style 1 required_configs: - cloud - runtime - runtime@thiskit --- # kit.yml required configs style 2 required_configs: cloud: true runtime: [blueprint new] funky: false
๐ In the first style, all hooks will require the listed configurations. In
๐ the second style,cloud
config will always be required,runtime
will
๐จ only be required when processingblueprint
andnew
hooks, andfunky
will never be required.0๏ธโฃ By default, if no
required_configs
block is specified, onlycloud
config
๐จ is requred when processingblueprint
, and no other hooks. This is
effectively the previous behaviour.Add
move_secrets_to_credhub
bash helper functionmove_secrets_to_credhub src_path:key dst_path
๐ This will move a secret under the environments Vault area to the
environments credhub area. Do not include the secrets base before the
๐src_path
, or the bosh env/deployment prefix before thedst_path
.Derived features are features that are artificially created by the
hooks/features script to facilitate absent of other features or a specific
๐ combination of features, so that secrets can be better specified (ie a
secret that only exists if a feature ISN'T specified) They must start with
a+
, are not checked with the validation features, and cannot be
explicitly stated in an environment file.๐ Bug Fixes
๐ Kit releases that preceed the current version by 30 or more releases are no
longer reported as non-existant.โ Compiled kits no longer contain the spec tests and kit devtools, as they
aren't needed to use the kit.๐ Improved details given when hooks fail, specifically when
blueprint
fails
๐ to determine which manifest fragments are requied for mergingDon't populate missing
maybe
paramsWhen a parameter is conditionally available, the
maybe:
parameter
dereference would prevent errors if the parameter was missing, but it would
leave an empty string as the value. This changes that behaviour to drop the
key or the array element that was being set to the missing parameter.