zip-tf

Packaging Terraform code into a safe ZIP involves creating a clean, timestamped archive while excluding build artifacts and sensitive tfvars files. This process regenerates the ORM schema and verifies the output to guarantee no secrets remain before saving to the zipped/ directory.

Excluding sensitive tfvars during Terraform zipping is handled automatically by pruning these files before archiving. The packaging process verifies the final ZIP artifact to ensure no disallowed files or secrets are present in the output directory.

Regenerating the ORM schema during Terraform archiving updates the schema definition prior to creating the ZIP file. This step ensures the packaged Terraform repository contains a freshly generated, accurate schema aligned with the current infrastructure code.

Automating Terraform verification before sharing is achieved by running safety checks that scan the packaged ZIP for secrets and disallowed files. This automated verification confirms the artifact is clean and safe for distribution or deployment.

Packaging Terraform repositories removes build artifacts from the final ZIP by cleaning the directory before archiving. This ensures the timestamped output contains only the necessary, verified Terraform assets without leftover build files.

Using a timestamped ZIP for Terraform distribution provides clear version tracking for your infrastructure archives. It organizes packaged assets in the zipped/ directory with unique names, simplifying rollback and audit processes during deployment.