From fd0676ea29824c1b60ea53768ff59f3ce93b76da Mon Sep 17 00:00:00 2001 From: Wilken Rivera Date: Tue, 30 Jan 2024 06:40:06 -0500 Subject: [PATCH] Fix URL rewrite check error for DevDot portal Refer to job https://github.com/hashicorp/packer/actions/runs/7709708630/job/21011464094 --- website/content/docs/plugins/install-plugins.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/content/docs/plugins/install-plugins.mdx b/website/content/docs/plugins/install-plugins.mdx index 1919ff5fce1..4302db8473f 100644 --- a/website/content/docs/plugins/install-plugins.mdx +++ b/website/content/docs/plugins/install-plugins.mdx @@ -69,7 +69,7 @@ various outputs, like error messages. At initialization, Packer attempts to discover the plugins installed locally. The logic follows what's described in Configuring Packer's -[plugin directory](https://developer.hashicorp.com/packer/docs/configure#packer-s-plugin-directory) +[plugin directory](/packer/docs/configure#packer-s-plugin-directory) section. While Packer is not verbose during this step, you can peek into what it is discovering @@ -208,7 +208,7 @@ packer plugins install github.com/hashicorp/vagrant The command will install the plugin in the `PACKER_CONFIG_DIR` set, or its default location, which depends on the OS/environment, as documented in -[Configuring Packer](https://developer.hashicorp.com/packer/docs/configure#packer-s-plugin-directory). +[Configuring Packer](/packer/docs/configure#packer-s-plugin-directory). @@ -217,7 +217,7 @@ If you have obtained or built a plugin binary for your OS/Architecture and want use it with Packer, you can install it manually. For Packer to load the plugin, it must be named with the convention `packer-plugin-NAME`, and placed in Packer's plugin directory, as documented in -[Configuring Packer](https://developer.hashicorp.com/packer/docs/configure#packer-s-plugin-directory). +[Configuring Packer](/packer/docs/configure#packer-s-plugin-directory). For example, if your configuration directory is located in `~/.config/packer`, you can copy the binary to `~/.config/packer/plugins/packer-plugin-NAME`, and