upstream/packer
1
0
Fork 0
mirror of https://github.com/hashicorp/packer.git synced 2026-05-28 04:35:38 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Fix URL rewrite check error for DevDot portal (#12818)

Browse source 
Refer to job https://github.com/hashicorp/packer/actions/runs/7709708630/job/21011464094
This commit is contained in:
Wilken Rivera 2024-01-30 15:33:21 -05:00 committed by GitHub
parent ca066f73bf
commit 08d41c2679
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
website/content/docs/plugins/install-plugins.mdx
View file

@ -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).
</Tab>
<Tab heading="Manual installation">
@ -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