From 13b34e2c73f4d3e572140c78632ec1af82f3269e Mon Sep 17 00:00:00 2001 From: Adrien Delorme Date: Mon, 15 Feb 2021 15:13:36 +0100 Subject: [PATCH] Update 1.7-template-upgrade.mdx --- website/content/guides/1.7-template-upgrade.mdx | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/website/content/guides/1.7-template-upgrade.mdx b/website/content/guides/1.7-template-upgrade.mdx index 1d7f8c108..08eec9145 100644 --- a/website/content/guides/1.7-template-upgrade.mdx +++ b/website/content/guides/1.7-template-upgrade.mdx @@ -135,10 +135,12 @@ in the rest of the template. Here it is a brief explanation of each field: - `version` - Should follow the [version constraints](/docs/templates/hcl_templates/blocks/packer#version-constraints). -- `source` - Should have the plugin's organizational namespace on GitHub and its short name. Packer will be responsible -for determining the full GitHub address. - For example, if the source is `sylviamoss/comment`, Packer will download the binaries from `github.com/sylviamoss/packer-plugin-comment`. - To learn more about the source field, check out the [Source Address](/docs/plugins#source-addresses) documentation. +- `source` - Should have the plugin's organizational namespace on GitHub and its + short name. Packer will be responsible for determining the full GitHub + address. For example, if the source is `github.com/sylviamoss/comment`, Packer + will download the binaries from `github.com/sylviamoss/packer-plugin-comment`. + To learn more about the source field, check out the [Source + Address](/docs/plugins#source-addresses) documentation. - `local_name`- Can be replaced with whatever you want, and the new value will become the name of the plugin. For example: ```hcl