TrustRadius: an HG Insights company
HashiCorp Packer Logo

HashiCorp Packer Reviews and Ratings

Rating: 8.8 out of 10
Score
8.8 out of 10

Reviews

1 Review

Best Image Builder in Market

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

We mainly use packer for creating Images on the fly with required tunning and use it with Our Configuration management tools or any IAC tool. We integrate Packer with multiple frameworks such as Chef or Puppet to install and configure the software. It acts for me as Machine Image As A Code. The main scope for us to use Packer is to automate our Image creation process and get away from the Golden Image concept so that we can bring Updated images in an automated way.

Pros

  • Multi-provider portability
  • Greater testability
  • Super fast infrastructure deployment

Cons

  • Manageability
  • Manageability
  • Manageability

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.