From 76fb0515affa31c77e34c3f23ed983af2423a0f4 Mon Sep 17 00:00:00 2001 From: Tony Carmichael <1105554+aicarmic@users.noreply.github.com> Date: Thu, 13 Aug 2020 09:40:52 -0600 Subject: [PATCH] Update publishing.html.md Clarify steps for sending in GPG keys if publishing with a GH org. --- website/docs/registry/providers/publishing.html.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/website/docs/registry/providers/publishing.html.md b/website/docs/registry/providers/publishing.html.md index ec11b7147..c5ca8fd18 100644 --- a/website/docs/registry/providers/publishing.html.md +++ b/website/docs/registry/providers/publishing.html.md @@ -92,11 +92,15 @@ $ gpg --armor --export "{Key ID or email address}" #### Individuals -If you would like to publish a provider under your username (not a GitHub organization), you can add your GPG key to the Terraform Registry by visiting [User Settings > Signing Keys](https://registry.terraform.io/settings/gpg-keys). +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. You can email it to terraform-registry@hashicorp.com, or your HashiCorp contact person (if you have one). +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