-
Notifications
You must be signed in to change notification settings - Fork 30
Use CRT for releases and CI #67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Release version is specified when manually triggering the build workflow. Go version is determined using the .go-version file. Will build for arm, arm64, 386, and amd64 now instead of just amd64.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. FWIW I would support leaving the final layer publish step in CircleCI for now. Rel-eng have a ticket to track adding support for publishing AWS Lambda layers, so switching directly to that in the future might be an easier option for us.
.release/ci.hcl
Outdated
github { | ||
organization = "hashicorp" | ||
repository = "vault-lambda-extension" | ||
release_branches = ["main", "VAULT-5260/use-crt"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leaving a comment as a reminder we should remove the test branch before merging.
and only build for arm64 and amd64
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this is ready to go if testing goes smoothly 👍
Tested both arm64 and amd64 binaries, and they seem to work, so I think we're good here 👍 |
Release version is specified when manually triggering the build workflow. Go version is determined using the .go-version file. Will build for arm64 as well as amd64.
TODO:
[ ] Setup AWS layer releases in a GitHub workflow(this will be done in another repo)