From 372750bd1b49fa3a83b6b42928fb130a630eaccc Mon Sep 17 00:00:00 2001 From: Sai Diliyaer Date: Sat, 5 Mar 2022 20:38:38 +0800 Subject: [PATCH] Website: Fix the hashicorp/packer link on the plugins creation page (#11629) It's currently linked to `github.com/packer` which seems to be an unrelated personal GitHub repo. --- website/content/docs/plugins/creation/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/plugins/creation/index.mdx b/website/content/docs/plugins/creation/index.mdx index e8ea99269..4a72cca06 100644 --- a/website/content/docs/plugins/creation/index.mdx +++ b/website/content/docs/plugins/creation/index.mdx @@ -232,7 +232,7 @@ To help with the discovery of remote Packer plugins on GitHub, plugins maintaine The registration process requires the creation of a `docs.zip` file archive containing the `.mdx` files for each of the plugin components in the remote plugin's repository. A working example can be seen at the [packer-plugin-docker repository](https://github.com/hashicorp/packer-plugin-docker/releases/latest). -Once in place the remote plugin can be added to Packer's website builds by opening a pull-request against [hashicorp/packer](https://github.com/packer), with the needed configuration for pulling in the remote documentation. +Once in place the remote plugin can be added to Packer's website builds by opening a pull-request against [hashicorp/packer](https://github.com/hashicorp/packer), with the needed configuration for pulling in the remote documentation. Remote plugins will have their components listed under the respected types (i.e builders, provisioners, etc) using the names specified in the remote block configuration, and labeled with their respective [tier and namespace](/docs/plugins#tiers-and-namespaces).