Way to go for new builder implementation

27 views
Skip to first unread message

Marc Falzon

unread,
May 19, 2020, 12:59:12 PM5/19/20
to Packer
Hello,

I'm about to start implementing a new builder, and upon reading the official documentation I've learned about Packer's plugins but I am a bit confused as to if it is the official way to implement new functionalities to Packer nowadays: are contributors expected to implement support for new builders/post-processors/etc as "community" plugins in external repositories (pretty much as Terraform does for providers), or to submit pull requests to the official Packer project's repository? I'm asking this because in the list of community builders the vSphere one is marked as deprecated as it's been "merged into official Packer repository and released with Packer since version 1.5.2".

Cheers,

m.

Megan Marsh

unread,
May 19, 2020, 1:07:39 PM5/19/20
to packe...@googlegroups.com
Good question. Moving forward, the vast majority of builders are going to be community-based like Terraform does. VSphere got merged because we already head VMWare support and we're hoping to clean up the official support for VMWare. It was easier to merge that particular builder and keep working on it instead of duplicating work internally. But for most builders, especially ones that don't already have some kind of support inside the Packer core, "community" is how it's going to go. 

--
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/f99e3295-a07a-477a-8bd1-a22ae5e8f736%40googlegroups.com.

Marc Falzon

unread,
May 20, 2020, 2:51:43 AM5/20/20
to packe...@googlegroups.com
Thank you for this clarification, I will proceed this way then.

Reply all
Reply to author
Forward
0 new messages