Skip to content
This repository has been archived by the owner on Jan 12, 2024. It is now read-only.

Releases: Nike-Inc/cerberus-lifecycle-cli

v0.15.2

18 Mar 00:11
Compare
Choose a tag to compare
  • Gateway config updated:
    • Health-check should return a content type and response body (more user friendly if you hit it from a browser)
    • Added a robots.txt to disallow crawling

Re-run create-gateway-config to apply to your environment.

v0.15.1

17 Mar 18:13
Compare
Choose a tag to compare
  • Adding error code to exit on error

v0.15.0

16 Mar 22:02
Compare
Choose a tag to compare
  • Added YAML support for standing up new Cerberus environments.
  • Added new restore complete command that allows for restoring a complete backup created by the x-region-backup-lambda.

v0.15.0-RC2

14 Mar 21:17
Compare
Choose a tag to compare
v0.15.0-RC2 Pre-release
Pre-release
  • Add restore complete command

v0.14.2

02 Mar 00:02
Compare
Choose a tag to compare
  • Bug fix: adding back deleted enum because it caused JSON parse error in some environments

v0.15.0-RC

27 Feb 00:35
Compare
Choose a tag to compare
v0.15.0-RC Pre-release
Pre-release
  • Added Restore Complete command.

v0.14.1

01 Feb 22:51
Compare
Choose a tag to compare

Minor fix around version reported by CLI (version 0.14.0 was self-reporting as v0.13.0).

v0.14.0

19 Jan 20:46
Compare
Choose a tag to compare

Adds optional parameters for desired, maximum, and minimum instances counts for create cluster and update stack calls.

Optional parameters are now enabled for gateway, cms, consul, and vault clusters.

v0.14.0-RC

19 Dec 04:05
Compare
Choose a tag to compare
v0.14.0-RC Pre-release
Pre-release

Added YAML DSL support for defining a Cerberus environment, to improve the UX of environment creation and maintenance.

v0.13.0

14 Dec 23:52
Compare
Choose a tag to compare

Add new param to pubish-dashboard that allows users to point to another artifact when publishing the dashboard to s3. The 2 artifacts will get merged on command execution before being uploaded to S3. This can allow for custom help pages, or possible custom data files with externalized content.