v3.0.9
Bug Fixes
-
Genesis will no longer try to build the manifest if the check for
prerequisites fails, such as cloud config or secrets are missing. -
When running compile-kit (ck) from a deployments directory, it would
look in the dev directory for the kit contents. However, if the dev
directory was a symlink, it would not follow the correctly dereference
the symlink, resulting in a compiled kit that just contained a symlink. -
This fixes a bug where when not using the self-signed haproxy certs in the cf
kit, the user would be prompted for the haproxy_ca:certificate and
haproxy_ca:key secrets, even though they are not used.The code that accepted the user input was also broken, and did not
store the user input correctly. -
The upstream cf-app-autoscaler does not specify alternative names for
the certificate, so we need to use the common name as the only
alternative name. -
Fixes issue when generating a self-signed certificate, the CA
certificate was not being returned.
Improvements
-
The upstream autoscaler uses an esoteric syntax for variable
references that prefixes the variable name with a ! after the double
parenthesis. This change allows the vaultification process to detect
and handle these references. -
If using search target mode, and you provide an exact match to the
desired deployment name, it will now only match that deployment
instead of listing all deployments that contain the given name. If
still using the -deployments suffix, this will be considered an exact
match without having to provide the suffix.Deployment matches that contain wildcards will still list all matching
deployments.