From a1128829995d32202b0882f67edf220b50771ef7 Mon Sep 17 00:00:00 2001 From: Megan Marsh Date: Wed, 13 Jan 2021 12:13:41 -0800 Subject: [PATCH] Update website/content/guides/1.7-plugin-upgrade/index.mdx Co-authored-by: Sylvia Moss --- website/content/guides/1.7-plugin-upgrade/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/guides/1.7-plugin-upgrade/index.mdx b/website/content/guides/1.7-plugin-upgrade/index.mdx index 09a1aa2b9..062c00934 100644 --- a/website/content/guides/1.7-plugin-upgrade/index.mdx +++ b/website/content/guides/1.7-plugin-upgrade/index.mdx @@ -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. \ No newline at end of file +We will soon write a follow-up guide explaining how to register you new plugin set with HashiCorp.