diff --git a/website/docs/registry/providers/publishing.html.md b/website/docs/registry/providers/publishing.html.md index c5ca8fd18..fc7a506b4 100644 --- a/website/docs/registry/providers/publishing.html.md +++ b/website/docs/registry/providers/publishing.html.md @@ -84,7 +84,8 @@ Before publishing a provider, you must first sign in to the Terraform Registry w All provider releases are required to be signed, thus you must provide HashiCorp with the public key for the GPG keypair that you will be signing releases with. The Terraform Registry will validate that the release is signed with this key when publishing each version, and Terraform will verify this during `terraform init`. -To export your public key in ASCII-armor format, use the following command: +- Generate a GPG key to be used when signing releases (See [GitHub's detailed instructions](https://docs.github.com/en/github/authenticating-to-github/generating-a-new-gpg-key) for help with this step) +- Export your public key in ASCII-armor format using the following command, substituting the GPG key ID created in the step above: ```console $ gpg --armor --export "{Key ID or email address}" @@ -96,7 +97,7 @@ If you would like to publish a provider under your GitHub username (not a GitHub #### Organizations -In order to publish a provider under a GitHub organization, your public key must be added to the Terraform Registry by a HashiCorp employee. Please send us an email to terraform-registry@hashicorp.com, including the information below, and one of us will get back to you shortly. For convenience, you may also use this Email template. +In order to publish a provider under a GitHub organization, your public key must be added to the Terraform Registry by a HashiCorp employee. Please send us an email to terraform-registry@hashicorp.com, including the information below, and one of us will get back to you shortly. For convenience, you may also use this email template. - GitHub organization (namespace): - Link to provider repository: