Genesis v2.7.23 Release Notes

Release Date: 2020-12-06 // over 3 years ago
  • ๐Ÿ‘Œ Improvements

    ๐Ÿ‘ Better deployment process and output, suppression of duplicate warnings.
    ๐Ÿš€ This change also allows kits to use the pre-deploy hook to validate
    conditions AFTER the manifest has been fully generated.

    Extract redacted vars file into repo (along with existing redacted manifest)
    ๐Ÿš€ after deployment.

    When a Genesis command needs access to BOSH, it would check if it was
    reachable. However, reachable does not mean accessible, so we now check
    that the user is authenticated with the BOSH director.

    ๐Ÿ‘Œ Improvements to generated when initializing a new Genesis
    repository. Thanks to Vasyl Tretiakov.

Previous changes from v2.7.22

  • ๐Ÿ‘Œ Improvements

    Pipeline: ci-show-changes now states explicitly when no differences were

    Unless explicitly a config of a given type is explicitly identified by name,
    ๐Ÿ”€ we now fetch and merge all configs of a given type (ie cloud, runtime) when
    a kit indicates that they are needed.

    ๐Ÿ› Bug Fixes

    ๐Ÿ‘ Better error message if genesis.env (and also params.env) is missing from
    the environment file.

    ๐Ÿš€ Pipeline: cpi configs are not associates with deployment, so there's no way
    to tell which version of the CPI configs were used on the previous
    ๐Ÿš€ deployment. Therefore, we now exclude cpi config in ci-show-changes.

    ๐Ÿš€ Auto-authenticate to vault after running a long-deployment so that exodus
    ๐Ÿš€ data could be added successfully was added a few releases back, but for kits
    that use credhub (ie cf-genesis-kit), access to the bosh director's exodus
    data (and thus vault) was needed to assemble the exodus data to be stored.
    This happened prior to reauthenticating to vault, and therefore failed.
    This has now been resolved.

    ๐Ÿ‘ Better support for multi-doc yaml: Ensure YAML partition is on a new line

    YAML files are text files, and text files (in *nix) consist of a series
    of lines, each terminated by a newline character, including the last
    ๐Ÿ”€ one. So this is the behaviour Genesis expected when merging multiple
    source YAML files into a multi-doc file.

    HOWEVER, certain editors don't naturally obey this spec, and when
    Genesis encountered these files in the wild, the "---\n" separator was
    appended to whatever the last value in the previous file was, which
    didn't result in a proper multi-doc file and data was corrupted. We now
    join with "\n---\n" just in case.