How do YOU version and store your completed packer images?

[Nate Dobbs]

This isn't an issue for packer per se but this may be the best place to discuss the topic. Those of you who have to share your images with other people, teams or organizations, how do you version, store and share your images? 

I'm at the drawing board on this topic and wanted to see how others in the community are handling these challenges with images that are complete. In my case in particular I have to share the images with both internal and external clients. Currently I'm using google drive for this but the versioning and uploading to the drive are not automated. The packer build files and build processes are stored in git so that part is covered nicely. 

Before I go down the path of solidifying google drive as the storage medium of choice, I'd like to hear from others. 

[Rickard von Essen]

We just include the git short hash in the name of the image (AMI) and tag with source AMI. But we only build cloud images and only for internal use.

--
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 "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/752f8c28-2eb4-4369-83da-ed42cea18a93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alvaro Miranda Aguilera]

not sure if an option, but perhaps you can have a git repo that they keep upto date with variables they can use?

--

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 "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/752f8c28-2eb4-4369-83da-ed42cea18a93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Gabo Kete]

There are plenty out there, Git Repo, Bitbucket, SourceForge , etc , not only helps you to save and share the files with other users but you have a version control that helps to know who, when and what changes were made in your files.. 

On Sunday, January 21, 2018 at 3:00:35 AM UTC+13, Alvaro Miranda Aguilera wrote:

not sure if an option, but perhaps you can have a git repo that they keep upto date with variables they can use?

On Fri, Jan 19, 2018 at 10:55 PM, Nate Dobbs <misconfi...@gmail.com> wrote:

This isn't an issue for packer per se but this may be the best place to discuss the topic. Those of you who have to share your images with other people, teams or organizations, how do you version, store and share your images? 

I'm at the drawing board on this topic and wanted to see how others in the community are handling these challenges with images that are complete. In my case in particular I have to share the images with both internal and external clients. Currently I'm using google drive for this but the versioning and uploading to the drive are not automated. The packer build files and build processes are stored in git so that part is covered nicely. 

Before I go down the path of solidifying google drive as the storage medium of choice, I'd like to hear from others. 

--
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 "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/752f8c28-2eb4-4369-83da-ed42cea18a93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Gabo Kete]

Ignore my answer.. Got your questions wrong..