iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update website/content/guides/1.7-template-upgrade.mdx 

Co-authored-by: Sylvia Moss <moss@hashicorp.com>
This commit is contained in:
Adrien Delorme 2021-02-15 17:24:56 +01:00 committed by GitHub
parent 8208f425c8
commit f7ee3f8ead
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
website/content/guides/1.7-template-upgrade.mdx
View File

@ -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.