From 49ce2399381ff97452bcb0fa1b23376be61e4d0a Mon Sep 17 00:00:00 2001 From: trujillo-adam Date: Tue, 28 May 2024 15:56:15 +0000 Subject: [PATCH] backport of commit 8796c74d71e6f4cfddfa86358cccad8ec89d29a8 --- website/content/docs/commands/init.mdx | 2 +- website/content/docs/configure.mdx | 2 +- website/content/docs/upgrade/v1_11.mdx | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/website/content/docs/commands/init.mdx b/website/content/docs/commands/init.mdx index 85090eeca..0159bd036 100644 --- a/website/content/docs/commands/init.mdx +++ b/website/content/docs/commands/init.mdx @@ -10,7 +10,7 @@ The `packer init` command initializes Packer according to an HCL template config ## Description -Use the `packer init` command to download and install plugins according to the `required_plugins` block in Packer templates written in HCL. Refer to [Specifying plugin requirements](docs/templates/hcl_templates/blocks/packer#specifying-plugin-requirements) in the template configuration reference for additional information about configuring the `required_plugins` block. +Use the `packer init` command to download and install plugins according to the `required_plugins` block in Packer templates written in HCL. Refer to [Specifying plugin requirements](/packer/docs/templates/hcl_templates/blocks/packer#specifying-plugin-requirements) in the template configuration reference for additional information about configuring the `required_plugins` block. Legacy JSON templates are not supported. You can convert your JSON template files to HCL using the [hcl2_upgrade](/packer/docs/commands/hcl2_upgrade) command. diff --git a/website/content/docs/configure.mdx b/website/content/docs/configure.mdx index 6887453dd..1b0f8f98b 100644 --- a/website/content/docs/configure.mdx +++ b/website/content/docs/configure.mdx @@ -10,7 +10,7 @@ This topic describes how to configure Packer. The default configurations are sui ## Overview -You can set Packer-specific environment variables in a configuration file to configure Packer behavior globally. Install configuration files in the Packer configuration directory to implement the configurations. You can also install plugin files and their SHA256SUM files to the plugins subdirectory under the configuration directory. Refer to [Installing Plugins](/plugins/install) for instructions. +You can set Packer-specific environment variables in a configuration file to configure Packer behavior globally. Install configuration files in the Packer configuration directory to implement the configurations. You can also install plugin files and their SHA256SUM files to the plugins subdirectory under the configuration directory. Refer to [Installing Plugins](/packer/docs/plugins/install) for instructions. You can also define Packer settings in a JSON configuration file and add it to the execution path. This configuration method is deprecated. diff --git a/website/content/docs/upgrade/v1_11.mdx b/website/content/docs/upgrade/v1_11.mdx index c6ddc5ac4..7ad5970c0 100644 --- a/website/content/docs/upgrade/v1_11.mdx +++ b/website/content/docs/upgrade/v1_11.mdx @@ -9,15 +9,15 @@ This topic describes how to upgrade to v1.11. Refer to the [Packer v1.11 release ## Requirements -[comment]: < > (Delete this section if there is no content for it) + ## Upgrade from v1.10 -[comment]: < > (Describe the steps) + ## Upgrade from a version older than v1.10 -[comment]: < > (Delete this section if there is no content for it) + ## Troubleshooting