Closed therealvio closed 1 year ago
Before merging, we need to verify the workflow works by setting up an appropriate PAT for this project so that it is able to stand up, and merge PRs for our Homebrew Tap.
@jamestelfer I can't try the tap. My PAT doesn't have enough access to make the changes without bypassing the reviewer requirements. We need to shift the PAT away from my own to a system-managed PAT. Refer to this GHA run.
Purpose π―
These changes publish new versions of
cfparams
to our Culture Amp Homebrew tap. To achieve this, the release Github Actions workflow is triggered via Buildkite. This invocation method enables the ability to pass Github access tokens without having to define them within this repo's secrets repository. This means, we can continue to have our secrets defined in AWS Secrets Manager and not have anything special for these kinds of workflows.Context π§
Notes π
A PAT for this repository was made so that a
goreleaser
PR could be created, and merged without approval in our Homebrew Tap.To test this, the default branch for the repo needed to be changed to this PR's branch. As well as extending the branch restrictions for the Buildkite pipeline.
The archive method opts in to use binaries rather than zipping and tarring it. This required us to rename the file as part of the install phase. This is so that the "" suffix is dropped and the binary and we're just left with
cfparams
as the installed binary name.