New Goreleaser and GitHub Actions-based release pipeline #464
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This new release pipeline has two parts:
A Gorelaser configuration that should produce build artifacts matching the layout required to publish the provider in the Terraform Registry.
A GitHub Action that workflow should be configured to automatically build and publish assets for release when a tag is pushed that matches the pattern
v*(ie.v0.1.0).Both the Goreleaser configuration and the release workflow are essentially unchanged from the version provided at:
https://github.com/hashicorp/terraform-provider-scaffolding
in order to share a consistent approach to building and releasing with other providers.