Multi component plugin naming

25 views
Skip to first unread message

watas...@gmail.com

unread,
Feb 20, 2021, 10:18:35 AM2/20/21
to Packer
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.

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.

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.

watas...@gmail.com

unread,
Feb 20, 2021, 10:33:15 AM2/20/21
to Packer
Oops, I noticed that there is a reference to the migration guide for such patterns...

I'm going to rename it to packer-plugin-amazon-ami-management.
2021年2月21日日曜日 0:18:35 UTC+9 watas...@gmail.com:

Megan Marsh

unread,
Feb 20, 2021, 10:37:36 AM2/20/21
to packe...@googlegroups.com
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

--
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 packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/446f0e82-8e6a-4ae9-93cf-01f3b2f3f38cn%40googlegroups.com.

Megan Marsh

unread,
Feb 20, 2021, 10:38:31 AM2/20/21
to packe...@googlegroups.com
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.
Reply all
Reply to author
Forward
0 new messages