v1.2.8

What's Changed

• chore(deps): dependency refresh by @cultureamp-renovate in #43

Full Changelog: v1.2.7...v1.2.8

v1.2.7

What's Changed

• ci: add release notifier to pipeline by @ctgardner in #44

New Contributors

• @ctgardner made their first contribution in #44

Full Changelog: v1.2.6...v1.2.7

v1.2.6

What's Changed

• Update README.md installation instructions by @jamestelfer in #24
• chore(deps): add renovate.json by @cultureamp-renovate in #26
• fix: update Backstage catalog ownership to match Github teams by @backstage-culture-amp in #27
• chore(deps): update goreleaser/goreleaser-action action to v5 by @cultureamp-renovate in #32
• chore(deps): update actions/setup-node action to v4 by @cultureamp-renovate in #31
• chore(deps): update actions/setup-go action to v5 by @cultureamp-renovate in #30
• chore(deps): update actions/checkout action to v4 by @cultureamp-renovate in #29
• chore(deps): dependency refresh by @cultureamp-renovate in #33
• chore(deps): update dependency golangci-lint to v1.58.2 by @cultureamp-renovate in #37
• chore(deps): update dependency golangci-lint to v1.59.1 by @cultureamp-renovate in #39
• chore(deps): update goreleaser/goreleaser-action action to v6 by @cultureamp-renovate in #38
• chore(deps): update golangci/golangci-lint-action action to v6 by @cultureamp-renovate in #36
• chore(deps): dependency refresh by @cultureamp-renovate in #34
• ci: upgrade goreleaser parameters by @jamestelfer in #40
• ci: update GoReleaser config to v2 by @jamestelfer in #42
• chore(deps): dependency refresh by @cultureamp-renovate in #41

New Contributors

• @jamestelfer made their first contribution in #24
• @cultureamp-renovate made their first contribution in #26

Full Changelog: v1.2.5...v1.2.6

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)" \
  ...