From df008f9ece45522cb697037baccb2cf357d609d5 Mon Sep 17 00:00:00 2001 From: Justin Campbell Date: Tue, 22 Sep 2020 09:37:26 -0400 Subject: [PATCH] website: Update Registry key management docs (#26299) --- website/docs/registry/providers/publishing.html.md | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/website/docs/registry/providers/publishing.html.md b/website/docs/registry/providers/publishing.html.md index 1f9a7d8e4e..7b717eb450 100644 --- a/website/docs/registry/providers/publishing.html.md +++ b/website/docs/registry/providers/publishing.html.md @@ -107,17 +107,8 @@ All provider releases are required to be signed, thus you must provide HashiCorp $ gpg --armor --export "{Key ID or email address}" ``` -#### Individuals +The ASCII-armored public key to the Terraform Registry by going to [User Settings > Signing Keys](https://registry.terraform.io/settings/gpg-keys). You can add keys for your personal namespace, or any organization which you are an admin of. -If you would like to publish a provider under your GitHub username (not a GitHub organization), you may add your GPG key directly to the Terraform Registry by going to [User Settings > Signing Keys](https://registry.terraform.io/settings/gpg-keys). - -#### 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. - -- GitHub organization (namespace): -- Link to provider repository: -- GPG Key: (paste here or attach) ### Publishing Your Provider