Skip to content
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.

Sign up for GitHub

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

Jump to bottom

DEVOPS 971: use new gpg key #2

Closed
wants to merge 1 commit into from
Closed

DEVOPS 971: use new gpg key #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,8 @@ jobs:
id: import_gpg
uses: crazy-max/ghaction-import-gpg@v5.0.0
with:
gpg_private_key: ${{ secrets.GPG_PRIVATE_KEY }}
passphrase: ${{ secrets.PASSPHRASE }}
gpg_private_key: ${{ secrets.GPG_ARTIFACT_SIGNING_KEY }}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same question on key change compatibility here

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sha256 sum file is being signed and a signature is created. People can download our publically accessible key and verify like this:

gpg --verify terraform-provider-awsapigateway_0.2.0_SHA256SUMS.sig terraform-provider-awsapigateway_0.2.0_SHA256SUMS

If there's documentation to verify our distribution, we may need to modify that, but I don't think anything else is needed here.

@ravisingal thoughts?

passphrase: ${{ secrets.GPG_ARTIFACT_SIGNING_PASSPHRASE }}

- name: Run GoReleaser
uses: goreleaser/goreleaser-action@v4.2.0
Expand Down