terraform-null-label
packer-examples-for-vsphere
Our great sponsors
| terraform-null-label | packer-examples-for-vsphere | |
|---|---|---|
| 2 | 8 | |
| 594 | 742 | |
| 2.4% | 5.0% | |
| 4.4 | 9.3 | |
| 1 day ago | 3 days ago | |
| HCL | HCL | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terraform-null-label
-
Enable/Disable resources conditionally
I came across CloudPosse's configurations and they've done a good job there, only thing is that I think there are too many interlinked configurations to achieve that and it sounds a bit overkill for our use case.
-
Terraform best practices?
Use terraform-null-label to help you name and tag correctly. See https://github.com/cloudposse/terraform-null-label/ for more details.
packer-examples-for-vsphere
-
OS cleaning for VMware template.
VMware have samples here https://github.com/vmware-samples/packer-examples-for-vsphere
-
Anyone have luck building images using Packer? Racking my brain.
I also want to add that I modeled my config out of this: https://github.com/vmware-samples/packer-examples-for-vsphere/tree/main
-
Linux Sysadmin trying to wrap his head around this..
Yeah I think I understand that bit. The only thing I didn't really understand was this example. Everything is defined in that one hcl file including compute resources.
-
Packer w/ vsphere-iso: Turn off WinRM + Sysprep before creating template?
Could anyone help show what I could do for a deployment using https://github.com/vmware-samples/packer-examples-for-vsphere that gets WinRM disabled and a sysprep implemented before the template is created? This just isn't clicking.
- Script to update Template's Windows Updates
- Multiple "Copies" of an individualized Ubuntu distribution
- Problem: Installing Tools on an Automated Template Build
-
Can you share with me your workflows and how you use the tools to deploy new infrastructure/applications?
Packer to build regular templates, VMware has an example repo of this: https://github.com/vmware-samples/packer-examples-for-vsphere
What are some alternatives?
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
terraform-aws-jenkins - Terraform module to build Docker image with Jenkins, save it to an ECR repo, and deploy to Elastic Beanstalk running Docker stack
terraform-best-practices - Terraform Best Practices for AWS users
bento - Packer templates for building minimal Vagrant baseboxes for multiple platforms
terraform-aws-nat-instance - Terraform module to provision a NAT Instance using an Auto Scaling Group and Spot Instance from $1/month
packer-ubuntu20.04 - Packer vsphere-iso builder for Ubuntu-20.04
checkov - Prevent cloud misconfigurations and find vulnerabilities during build-time in infrastructure as code, container images and open source packages with Checkov by Bridgecrew.
HashiCorp-Cloud-Guide - HashiCorp Cloud Guide
Packer-vsphere - Packer-vsphere
terraform-provider-sops - A Terraform provider for reading Mozilla sops files
terraform-docs - Generate documentation from Terraform modules in various output formats