Skip to content

Releases: genesis-community/vault-genesis-kit

v1.4.0

05 Mar 22:19
Compare
Choose a tag to compare

Improvements

  • Updated Safe-Boshrelease to v0.2.0

Software Components

Name Version Release Notes
safe-boshrelease v0.2.0 Release Notes

v1.3.0

12 Dec 21:44
Compare
Choose a tag to compare

Improvements

  • Use Xenial stemcells by default

v1.2.1

17 Sep 18:17
Compare
Choose a tag to compare

Improvements

  • Added auxiliary-vault parameter, which when set to true will skip the
    automatic initialization and unseal after deploy. This should be set to true
    when deploying a Vault for non-Genesis related secret storage. The default is
    false.

v1.2.0

03 Jun 17:45
Compare
Choose a tag to compare

This release marks a milestone for the Vault Genesis Kit in
particular, and for Genesis as a larger ecosystem; this is the
first version of the Vault Genesis Kit to support the newfangled
features and capabilities of Genesis 2.6.

Genesis 2.6 is a backwards-compatible, yet forward-thinking
iteration on the Genesis v2 codebase. While it maintains the
concept of kits and environment files (a mainstay of Genesis), it
expands upon the power given to kit authors, and helps them help
operators in a more constructive fashion.

This release of the Vault Genesis kit requires that you
upgrade to Genesis v2.6.0 or greater. (Obviously, for
security reasons and bug fixes, you'll want to choose the latest
available release)

New Features

  • Azure is now automatically detected by the kit, via the BOSH CPI
    reported by the targeted director. This means that the swap-out
    of availability zones (a BOSH concept) for availability sets (an
    Azure concept) is seamless, and does not require a feature flag
    to be set in your environment files.

  • The genesis do <env> -- target addon task sets up a safe
    target for you, by interrogating BOSH for the possible node IPs,
    and trying each in turn until one answers.

  • The genesis do <env> -- init addon task allows you to
    initialize a newly-deployed Vault, with minimal hassle.

  • The genesis do <env> -- seal and genesis do <env> -- unseal
    addons allow you to seal and unseal a deployed Vault, without
    having to remember the appropriate safe commands, and without
    mucking about with your current safe target.

  • The genesis do <env> -- status addon will inform you of health
    and availability of the Vault nodes, and their seal status.

  • New pre-deploy and post-deploy hooks now safely unseal the Vault
    after a successful deployment, without you having to provide
    concourse with the seal keys directly, and without storing them
    "in the clear" anywhere.

v1.1.0

25 Jan 05:21
Compare
Choose a tag to compare

Release Engineering

We're trying out a new Concourse CI/CD pipeline for automating the
testing, vetting, and releasing of Genesis Kits, and this kit is
in the trial runs.

1.0.2

08 Jan 15:01
5f62043
Compare
Choose a tag to compare

Updated Shield subkit with embedded proxy support

v1.0.1

05 Jan 19:54
49cb3d1
Compare
Choose a tag to compare
v1.0.1 Pre-release
Pre-release

Upgrade shield subkit to support v8.0.4.

v1.0.0

13 Dec 21:01
Compare
Choose a tag to compare

Changes

v0.1.1

10 Nov 04:26
Compare
Choose a tag to compare
v0.1.1 Pre-release
Pre-release

v0.1.1

v0.1.0

28 Apr 15:08
Compare
Choose a tag to compare
v0.1.0 Pre-release
Pre-release

Initial Release