Infrastructure & Delivery Code Hygiene

Terraform, container, Kubernetes, and CI workflow hygiene.

Choose a focused Infrastructure & Delivery recipe

This collection contains 7 bounded Infrastructure & Delivery workflows. Choose the recipe whose objective matches the repository evidence instead of combining unrelated cleanup into one run.

• Terraform format, validation, and provider-lock hygiene: Use it to keep configuration canonical and provider resolution reproducible.
• Terraform state-address and refactor safety: Use it to preserve resource identity through module and address refactors.
• Dockerfile layer, cache, and build-context hygiene: Use it to make container builds reproducible, cache-efficient, and free of accidental context.
• Container signal, healthcheck, and shutdown hygiene: Use it to make PID 1 signal handling, readiness, health, and graceful shutdown correct.
• Kubernetes schema, deprecation, and selector drift: Use it to remove deprecated fields and prevent selector and label contract drift.
• Kubernetes probe, resource, and rollout hygiene: Use it to make probes, resources, disruption, and rollout settings internally consistent.
• CI workflow timeout, concurrency, and cache hygiene: Use it to bound CI jobs and prevent stale caches and duplicate workflow races.

How to use this collection

Read the repository’s configured runtime, compiler, framework, analyzer, and test commands before selecting a workflow. Start in audit mode, record file and symbol evidence, and authorize a fix only after the candidate scope is reviewable. Preserve supported versions, public behavior, and existing tool configuration.

If the evidence is a named CVE, scanner finding, exposed secret, authorization flaw, or injection path, use the focused vulnerability-remediation playbook instead of a code-hygiene recipe. Stop when the safe result requires an owner decision about architecture, compatibility, production data, or deployment state.

Full recipe list