v1.2.5

What's Changed

• chore: cfparams is changing default branch to main by @therealvio in #25

Full Changelog: v1.2.4...v1.2.5

v1.2.4

What's Changed

• ci: Releases are pushed to Culture Amp Homebrew tap by @therealvio in #21

Full Changelog: v1.2.3...v1.2.4

v1.2.3

What's Changed

• project is cfparams, not reporting by @therealvio in #23

Full Changelog: v1.2.2...v1.2.3

v1.2.2

What's Changed

• chore: Deploy role is not required for cfparams by @therealvio in #22

Full Changelog: v1.2.1...v1.2.2

v1.2.1

What's Changed

• Document extra tagging functionality by @chloeruka in #12
• Add Homebrew installation instructions. by @toothbrush in #13
• Adding catalog-info for Sock-keeping day by @n-tucker in #14
• fix: update Backstage catalog ownership to match Github teams by @backstage-culture-amp in #15
• chore: update golang dependencies by @ngocpea in #16
• chore: upgrade goland dependencies by @ngocpea in #17
• chore: Add autosilk-cli.yaml by @therealvio in #19
• fix(autosilk): environment and policies key are required by @therealvio in #20
• chore: Distribute ARM releases via GoReleaser by @therealvio in #18

New Contributors

• @toothbrush made their first contribution in #13
• @n-tucker made their first contribution in #14
• @backstage-culture-amp made their first contribution in #15
• @ngocpea made their first contribution in #16
• @therealvio made their first contribution in #19

Full Changelog: v1.2.0...v1.2.1

v1.2.0: Extended Tag support

• Support extra tags defined as CLI arguments

Tags can now also be overridden and added to on the command line, just like parameters can:

#tags-test.yaml
asset: buildkite
workload: delivery
buildkite-group: build-test

> cfparams --tags=tags-test.yaml buildkite-group=build-pylons message=extra-tag

[
  {
    "Key": "buildkite-group",
    "Value": "build-pylons"
  },
  {
    "Key": "message",
    "Value": "extra-tag"
  },
  {
    "Key": "asset",
    "Value": "buildkite"
  },
  {
    "Key": "workload",
    "Value": "delivery"
  }
]

v1.1.0: tags

• Support YAML stack tag files via --tags (details below)
• Use Go modules (Go 1.11+) rather than dep.

Stack Tags

CloudFormation stacks can be tagged, and those tags flow into all taggable resources the stack creates. As with --parameters, the aws cloudformation commands expect these in an awkward format. cfparams --tags file.yaml helps.

# tags-production.yaml
Name: Widgets as a Service
asset: widget-api
workload: production

cfparams --tags=tags-production.yaml

[
  {
    "Key": "Name",
    "Value": "Widgets as a Service"
  },
  {
    "Key": "asset",
    "Value": "widget-api"
  },
  {
    "Key": "workload",
    "Value": "production"
  }
]

Usage with AWS CLI:

aws cloudformation create-stack \
  ... \
  --tags "$(cfparams --tags=tags-production.yaml)" \
  ...

v1.0.0: “stable”

v1.0.0 references the same code as v0.3.0, it's being promoted to stable as per https://semver.org/#how-do-i-know-when-to-release-100

v0.3.0: !ParameterStore

• Support !ParameterStore /foo/bar in parameters YAML files (#7)
• Handle blank/missing values (#9, fixes #8)
• dependencies (YAML parser etc) managed by dep
• Release downloads are .tar.gz not .gz so executable file mode on the binary is retained.

Versioning as v0.3.0 rather than v0.0.3 or v0.1.0 due to added features and to avoid confusion. A v1.0.0 should be tagged soon after this.

v0.0.2: Handle blank defaults

#6 Fixed bug where accept-defaults ignored defaults that were empty strings ("").