Automate releasing kubectl-mongodb plugin using goreleaser
#351
Conversation
This file contains hidden or 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
…easer Apart from running goreleaser to release the plugin we also need to upload the release artifacts to the S3 bucket. That's what this commit does.
viveksinghggits
added
the
skip-changelog
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.
Summary
Since we can not notarize the
kubectl-mongodbbinary in dev/staging workflow, we won't be able to just promote those binaries when we are planning to release the product. That's why while releasing thekubectl-mongodbplugin we will have to build the binary again using goreleaser, which involves creating release artifacts, notarizing/signing the binary and uploading the release artifacts to the github release as assets.This PR adds a python script that does that.
Proof of Work
ToDo
Checklist
skip-changeloglabel if not needed