v1.1.0

Improvements

• Added MANUAL.md to explain how to create and customize a bosh release manifest as a genesis-deployable kit.

• Allow alternative name for the base manifest yaml file. It used to require that the file be ops/base.yml but now can also use ops/<type>.yml where is the name of the deployment repo specified by the genesis init command. (e.g. if genesis init -k generic postgres was used, the kit would use ops/postgres.yml as the base manifest file, which is convenient because you can then just copy the contents of the postgres-release's templates directory into ops/ and it just works)

• Updated stemcells to ubuntu-jammy and the minimum genesis version to 2.8.10

v1.0.1

Improvements

• Updated README.md file to better explain how to build specific deployments using the generic kit.

• Can now just put the full manifest in the environment file for one-off deployments, though best practice is still to put the base manifest in ops/base.yml to make pipeline deployments meaningful and safe.

Bug Fixes

• Fixes user-side addon support

• Error occurring with environments that are generated via the genesis new command has been fixed; please regenerate your environment, or simply replace params: [] with params: {}

Generic Genesis Kit v1.0.0

Initial Release

This kit is designed to wrap existing BOSH deployment manifests to provide Genesis tooling, such as secrets management, pipelines, exodus data and deployment histories.