Thank you for stopping by. This is a little pet project that I am attempting to modularize packer templates to make them as plug and play as possible.
Still a work in progress, but aiming for a minimally viable solution to quickstart packer adoption.
I love Packer. Probably, too much. I also love Terraform. When it comes to anything from HashiCorp, I lean to the infrastructure side of things. For this I am trying to replicate what Terraform modules do which make provisioning resources and architecture with Terraform much simpler.
I am also trying to share this with the community to more quickly adopt Packer and HCP Packer into their workloads.
At first this won't be too robust, but will allow for simple and practical methods to build images in the cloud. I will keep authentication mainly with a username + password, but I will link to documentation if looking to use alternative authentication.
For the major public clouds, I am referring to:
- AWS
- Azure
- Google Compute Engine
Looking to have only two templates.
One for your base images and one for your app images.
Those templates will run on one or many cloud platforms.
Those tempaltes will run windows or linux.
Got HCP Packer? Good.
I will have a bool variable which can be set to true or false to start sending meta data to HCP Packer.
Bucket name and labels are customizable in the var-file.
I will try to leave this as flexible as possible.
When I think of flexibility I think of where to build, what to build, how to build.
Some examples and thoughts:
- Toggle to enable HCP Packer.
- Toggle to override which cloud platforms to build on.
- Specify the OS type : Linux or Windows which would then affect downstream build steps.
- Var-Files which will be the preferred method to make this plug and play.