v2.8.11-rc.2

This is a prerelease - please see commit messages for changes

v2.8.11-rc.1

This is a prerelease, containing:

Improvements

• Genesis *-kit commands no longer need to validate to vault, as they
  don't use vault.

• Improved method of accessing the genesis perl library without losing
  access to the local perl5 library.

Bug Fixes

• Vault initialization looks in the right place for namespace and
  strongbox settings in the secret-provider configuration

• Updates expected output from updated SSL libraries for creation of
  dhparams and validation of X509 signing cert

• Fixes error caused when env file was a multi-page file that contained
  go-patch style pages.

Full Changelog: v2.8.10...v2.8.11-rc.1

v2.8.10

Bug Fixes

• Fix syntax error that breaks in recent vintage of Perl (blindly
  ignored in previous versions)

• Resolves issue encountered when creating a new proto bosh
  environment. Specify either --bosh-env <name> or --create-env to
  specify the parent BOSH environment or to have no parent bosh (via
  bosh create-env).

• Resolves issue when running genesis man <env>.yml - the .yml can now
  be omitted or left in.

• Fixes current directory when editing environment file after genesis new

• Detects newer versions of BOSH CLI that install with the executable
  named bosh-cli

• Make downloaded kits readable by all. Originally they were only
  readable by the user who downloaded them, but if you're working in a
  shared environment (with sticky group), this meant others couldn't
  deploy or do anything that involved reading the kit.

• Some X509 certs have more complicated Issuer and Subject lines, which
  were not correctly parsed. This has been resolved.

Improvements

• Add genesis edit <env> command

  This allows you to edit your environment files side-by-side with the
  manual for the kit.

v2.8.10-rc.3

This is a prerelease - please see commit messages for changes

v2.8.9

Improvements

• Supports pages to ci.yml for better pipeline customizations. These
  pages can be either overlay-style (spruce) or go-patch style. These
  extra pages will be merged over the pipeline generated by Genesis.

  Because concourse syntax allows non-homogeneous structure, you can't
  always use spruce operators to overlay the right location (ie adding
  an additional param to a specific task config) In these cases, you
  can use go-patch.

  Example:

  ---
  pipeline:
    <... all the normal ci.yml configuration values ...>
  
  ---
  - type: replace
    path: /jobs/name=<env>/plan/0/do/task=bosh-deploy/config/params/MY_ENV?
    value: some-value
  
  

  Note that the first page must be in overlay style, not go-patch,
  because it must stand as a valid yaml hash on its own.

v2.8.8

Bug Fixes

• Fix issue with pipeline's show-changes task that was due to missing
  the BOSH environment.

v2.8.7

Bug Fixes

• For vaults that have different secrets mount, you can set
  VAULT_SECRETS_MOUNT in the pipeline job to specify an alternative
  location where the secrets are found. This fixes the issue where the
  pipeline can't authenticate to vault because it can't find handshake
  secret under /secrets/

• Pipeline fixes to authenticate to the vault when running errands

Improvements

• Pipeline jobs can now use email for status notifications.

• Pipeline can now specify an alternative image registry for resources
  and workers, for supporting closed networks. Supports both insecure
  and authentication by username/password.

v2.8.7-rc.10

This is a prerelease - please see commit messages for changes

v2.8.7-rc.6

This is a prerelease - please see commit messages for changes

v2.8.7-rc.5

This is a prerelease - please see commit messages for changes