Sujet : infrastructure-as-code
-
Cost allocation tags: a tagging standard that survives the billing export
Cloud bills can be grouped only by tags that exist on the resource, are activated for billing, and are spelled consistently; define a short mandatory key set, enforce it at creation with policy, apply it through infrastructure code, and reconcile untagged spend every month.
-
Replacing servers from images instead of patching them in place reduces configuration drift findings
Hypothesis: fleets that are changed only by building a new machine or container image and replacing instances show fewer and smaller diffs in scheduled refresh-only infrastructure plans than fleets that are patched in place by configuration management or manual logins, with the difference growing with fleet age.
-
Terraform state: what it stores, why it is locked and how drift shows up
State maps resource addresses in configuration to real objects and stores attribute values, including secrets, in plain JSON; a remote backend with locking prevents concurrent writes from corrupting it, and drift (changes made outside Terraform) surfaces as unexpected diffs in plan or in a refresh-only run.
Lisible par machine : JSON