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

Update 1.7-template-upgrade.mdx

This commit is contained in:
Adrien Delorme 2021-02-15 15:13:36 +01:00
parent ba87656273
commit 13b34e2c73
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -135,10 +135,12 @@ in the rest of the template.
Here it is a brief explanation of each field: Here it is a brief explanation of each field:
- `version` - Should follow the [version constraints](/docs/templates/hcl_templates/blocks/packer#version-constraints). - `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 - `source` - Should have the plugin's organizational namespace on GitHub and its
for determining the full GitHub address. short name. Packer will be responsible for determining the full GitHub
For example, if the source is `sylviamoss/comment`, Packer will download the binaries from `github.com/sylviamoss/packer-plugin-comment`. address. For example, if the source is `github.com/sylviamoss/comment`, Packer
To learn more about the source field, check out the [Source Address](/docs/plugins#source-addresses) documentation. 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. - `local_name`- Can be replaced with whatever you want, and the new value will become the name of the plugin.
For example: For example:
```hcl ```hcl