I'm currently diving into Infrastructure as Code (IaC) and have noticed that drift issues often arise from manual changes, sometimes referred to as ClickOps. I'm curious—how do you identify these drifts? Is there a way to track them effectively, or is it just not possible?
4 Answers
Sure, here's a quick flow: you create your Terraform code and apply it. If someone goes in and messes with things manually, your next apply will show those changes. It reverts everything back to what your code defines. So, you essentially keep track by regularly applying your configurations and fixing any deviations.
To really manage drift, it's essential to restrict ClickOps access completely. Only allow manual changes in development environments, not in production or testing phases. This way, your infrastructure remains intact, and you can focus on planning with IaC.
Before you even think about drift detection, you need to have IaC set up first. If there's no code to compare against, tracking changes is pointless. Get your IaC in place, then you can start worrying about drifts.
Drift detection depends heavily on your IaC tool. For instance, if you're using Terraform, just run a 'plan' command to see what would change. This allows you to spot any discrepancies caused by manual edits.

Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically