Likelihood to Recommend We use packer to generate new machine images for multiple platforms on every change to our Configuration Management tools like Chef/Puppet/
Ansible It's act single tool for Image building for Multi-provider like AWS/Azure/GCP Helps to achieve Dev/Prod Parity Packer itself doesn't have a state like
Terraform . You can't do packer output AMI ID. If you have a scenario where you want to maintain the state for images it would be tough to manage via Packer.
Read full review Pros Multi-provider portability Greater testability Super fast infrastructure deployment Read full review Cons Manageability Manageability Manageability Read full review Likelihood to Renew We are happy with the use of Packer in our organization. Apart from manageability, I don't find any other drawback with Packer.
Read full review Usability It's best for building Image with many features and benefits.
Read full review Support Rating I only once required support and it was very smooth.
Read full review Implementation Rating I haven't found any issue in Implementation that itself describes how well this tool is built.
Read full review Alternatives Considered There are lot of tools in market which does the job for Image creation but all of them are not complete Machine/Image as a code. All other alternatives can create Image partially. Main reason for selecting Packer are Packer is lightweight, portable, and command-line driven Packer helps keep development, staging, and production as similar as possible. Packer automates the creation of any type of machine image Multi-provider portability is the feature to die for
Read full review Return on Investment Super fast infrastructure deployment Quick turnaround of infrastructure in multiple cloud using single tool. Increase productivity by reducing time in infrastructure building. Read full review ScreenShots