If you get stuck on the migration, please open an issue and tag me (@swampdragons on github) and I'll PR your repo and give you a hand.
On Sat, Feb 20, 2021 at 7:37 AM Megan Marsh <[email protected]> wrote: > I'm not sure that guide answers your question, though. > > I think the right course of action would be to name your new repository > packer-plugin-amazon-ami-management > > Then, when you register the post-processor in the new server, make sure to > register it using the plugin.DEFAULT_NAME variable. That will tell Packer > to use the plugin root name (amazon-ami-management) as the reference name > for the post-processor. > > Then, open a docs PR so we can link to you from our "community > post-processors" page, or open an issue with a link to your new repo so I > can do it for you :D > > On Sat, Feb 20, 2021 at 7:33 AM [email protected] <[email protected]> > wrote: > >> Oops, I noticed that there is a reference to the migration guide for such >> patterns... >> https://www.packer.io/guides/1.7-plugin-upgrade#how-to-upgrade-the-plugin >> >> I'm going to rename it to packer-plugin-amazon-ami-management. >> 2021年2月21日日曜日 0:18:35 UTC+9 [email protected]: >> >>> Congratulations on the release of Packer v1.7.0! >>> >>> I'm an author of the post-processor plugin called >>> packer-post-processor-amazon-ami-management. >>> https://github.com/wata727/packer-post-processor-amazon-ami-management >>> >>> Following the release of v1.7, I'm working on upgrading the plugin. I >>> noticed the previous plugin architecture is deprecated and we should >>> migrate the plugin to the multi component plugin from this version. >>> >>> According to the documentation, it seems right to name my plugin >>> packer-plugin-amazon, but this is obviously not a good idea. >>> https://www.packer.io/docs/plugins/creation#naming-conventions >>> >>> What is the proper name for a plugin like my plugin that adds a >>> post-processor to the functionality of an existing cloud vendor (AWS) to >>> support automatic installation with packer init? Please tell us your >>> thoughts. Thank you. >>> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/hashicorp/packer/issues >> IRC: #packer-tool on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Packer" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/packer-tool/446f0e82-8e6a-4ae9-93cf-01f3b2f3f38cn%40googlegroups.com >> <https://groups.google.com/d/msgid/packer-tool/446f0e82-8e6a-4ae9-93cf-01f3b2f3f38cn%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/hashicorp/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CAGPV1urTFvQK64aXFAd0Tsc5GCxNDwt0VoTMsRYrvzbcOV4Ymg%40mail.gmail.com.
