From f7ee3f8ead5dd4f7008a67871144554021ed1172 Mon Sep 17 00:00:00 2001 From: Adrien Delorme Date: Mon, 15 Feb 2021 17:24:56 +0100 Subject: [PATCH] Update website/content/guides/1.7-template-upgrade.mdx Co-authored-by: Sylvia Moss --- website/content/guides/1.7-template-upgrade.mdx | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/website/content/guides/1.7-template-upgrade.mdx b/website/content/guides/1.7-template-upgrade.mdx index 08eec9145..5a90394ee 100644 --- a/website/content/guides/1.7-template-upgrade.mdx +++ b/website/content/guides/1.7-template-upgrade.mdx @@ -135,8 +135,8 @@ 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 +- `source` - Should have the GitHub hostname, the plugin's organizational namespace, 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 @@ -182,4 +182,3 @@ and won't need to run `init` again unless you want to upgrade the plugin version A template with a `required_plugins` block should **always** be initialised at least once with `packer init` before `packer build`. If the template is built before init, Packer will fail and ask for initialisation. -