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.
