Add support for more Packer builders

[xlr-8]

Thanks for the project, really nice!

I was wondering if you thought of extending this project's scope? The project is called packer-resource, but manages "only" AMI from packer.

Would you consider adding other builders than AMI ?
If this was meant for AWS only, do you consider building docker images for ECR ?

Src: https://www.packer.io/docs/templates/builders.html

Best,

[jdub]

Thanks -- I would definitely like to add non-AMI builders. I held off adding this to the community resources list because I thought it should work with multiple AMI outputs, non-AMI builders, etc. first.

[jdub]

… and just over a week later, I have my own use case for a Docker builder. 😄

Some thoughts on the problem space:

• We shouldn't break the current interface while adding other builders, e.g. the id file should remain for single AMI builds.
• We should think carefully about the outputs based on what might consume them. The id file works very well as an input into cloudformation-resource. What might consume the output for X builder? What is the most useful output, or outputs?
• We should handle multiple builders, so outputs should probably not step on each other.
• When using multiple builders, it would be super helpful to let triggers choose one (or more?) builders. e.g. when your Packer git repo updates, you want to trigger every builder. But when your ami-resource updates, it'd be nice to trigger just the AMI builder. Saves having multiple packer resources, which would probably be copypasta.