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

Update website/content/guides/1.7-plugin-upgrade/index.mdx 

Co-authored-by: Sylvia Moss <moss@hashicorp.com>
This commit is contained in:
Megan Marsh 2021-01-13 12:13:41 -08:00 committed by GitHub
parent 5d49a522c0
commit a112882999
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/content/guides/1.7-plugin-upgrade/index.mdx
View File

@ -21,7 +21,7 @@ github.com/hashicorp/packer with github.com/hashicorp/packer-plugin-sdk.
But some of the import paths have changed more than that because we've refactored the SDK some to make it easier to discover and use helpful modules. Here are a few common paths below:
github.com/hashicorp/packer-plugin-sdk/template/config => github.com/hashicorp/packer-plugin-sdk/template/config
github.com/hashicorp/packer/template/config => github.com/hashicorp/packer-plugin-sdk/template/config
github.com/hashicorp/packer/packer => github.com/hashicorp/packer-plugin-sdk/packer
github.com/hashicorp/packer/template/interpolate => github.com/hashicorp/packer-plugin-sdk/template/interpolate
@ -179,4 +179,4 @@ And then reference your plugin in the Packer template using "vsphere-iso" and "v
You can still use the `DEFAULT_NAME` constant with a set implementation; in this example, whatever you register with the DEFAULT_NAME will be referenced in the Packer template as "vsphere". You can only register one plugin per plugin set using the DEFAULT_NAME
We will soon write a follow-up guide explaining how to register you new plugin set with HashiCorp.
We will soon write a follow-up guide explaining how to register you new plugin set with HashiCorp.