Ok, you have two options 1) Distribute it as a standalone packer plugin, 2)
contribute it to the packer core plugins.
First some general info about the plugin system can be found here
<https://www.packer.io/docs/extend/plugins.html>. It's slightly outdated,
first all core packer plugins are now bundled in one binary *packer* and
there are no separate binary for say *packer-builder-amazon-ebs *anymore.
And *command *plugins are not supported any longer.
1) You can maintain your own repo with the code for your repo and
instructions to build/download it. For an old example see packer-parallels
The benefit is that you regain full control. The drawback is that less
users will find it and there is a extra installation step. Currently there
are no official list of 3pp plugins, but it have been talked about.
2) Open a PR to packer <https://github.com/mitchellh/packer>. Almost
everything in packer is a plugin, core plugins are distributed with packer
and now built in to a single binary. If your plugin is general and target
AWS I think it's at least a good candidate for a review of inclusion into
the packer core plugins.
On Monday, September 19, 2016 at 5:19:56 AM UTC+2, Scott Kellish wrote:
> Hi Rickard,,
> Thanks. I should have been more specific in my question. I've read the
> CONTRIBUTING.md which only talks about contributing changes the Packer
> source itself. My understanding that developing plug-ins (which is how I've
> implemented by post-processor) is the preferred method rather than
> submitting changes to the packer source. Do I just check me code into my
> own github account or is there something like a central "packer" github for
> publishing "plug-ins"?
> On Sunday, September 18, 2016 at 10:03:02 AM UTC-4, Rickard von Essen
>> Hi Scott,
>> The best way is to read CONTRIBUTING.md in the repo and open a pull
>> Looking forward to it.
>> On Sep 18, 2016 3:24 PM, "Scott Kellish" <skel...@comcast.net> wrote:
>>> New to this and didnt see a guideline anywhere. I developed a
>>> post-processor for creating encrypted versions of amis produced by the
>>> amazon-ebs builder that I would like to share.
>>> How do I go about doing that?
>>> 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
>>> GitHub Issues: https://github.com/mitchellh/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
>>> For more options, visit https://groups.google.com/d/optout.
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/mitchellh/packer/issues
IRC: #packer-tool on Freenode
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.