From 24f20177ee9c08cd23c3ff57d1346c5db4bb8cb4 Mon Sep 17 00:00:00 2001 From: Justin Campbell Date: Tue, 1 Sep 2020 15:04:39 -0400 Subject: [PATCH] website: Omitunnecessary instruction fror Registry The GitHub Action passes this in already. --- website/docs/registry/providers/publishing.html.md | 1 - 1 file changed, 1 deletion(-) diff --git a/website/docs/registry/providers/publishing.html.md b/website/docs/registry/providers/publishing.html.md index c676e81c0..669cd90b4 100644 --- a/website/docs/registry/providers/publishing.html.md +++ b/website/docs/registry/providers/publishing.html.md @@ -54,7 +54,6 @@ To use GitHub Actions to publish new provider releases to the Terraform Registry 1. Copy the [GoReleaser configuration from the terraform-provider-scaffolding repository](https://github.com/hashicorp/terraform-provider-scaffolding/blob/master/.goreleaser.yml) to the root of your repository. 1. Copy the [GitHub Actions workflow from the terraform-provider-scaffolding repository](https://github.com/hashicorp/terraform-provider-scaffolding/blob/master/.github/workflows/release.yml) to `.github/workflows/release.yml` in your repository. 1. Go to *Settings > Secrets* in your repository, and add the following secrets: - * `GPG_FINGERPRINT` - The key fingerprint or ID of your GPG signing key. The fingerprint is outputted when listing keys with `gpg --list-keys`. * `GPG_PRIVATE_KEY` - Your ASCII-armored GPG private key. You can export this with `gpg --armor --export-secret-keys [key ID or email]`. * `PASSPHRASE` - The passphrase for your GPG private key. 1. Push a new valid version tag (e.g. `v1.2.3`) to test that the GitHub Actions releaser is working.