fix: Remove S3 integration from provider registry #14
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
valentindeaconu
added a commit
that referenced
this pull request
Jul 23, 2022
This was referenced Aug 13, 2022
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.
There's no need to integrate with S3 for provider registry since providers can be uploaded to GitHub releases, using tools such as Go Releaser.
Also, this PR introduces authorities, which hold the GPG public keys. A provider can be released under an authority, requiring the shasum files to be signed with the respective GPG public key - the same workflow Terraform registry uses.
The authority will be later used to generate API keys which can be used in release pipelines.