How do you manage DCIM and IPAM data in a GitOps workflow?
Infrastructure-as-code workflows break down when engineers have to account for unexpected manual changes and configuration drift. Introducing a new machine or changing an existing IP address manually forces teams to constantly chase and patch out-of-sync environments.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
- 1Using NetBox or Nautobot with Terraform or OpenTofu and Git as the source of truth
- 2pull tzdata ahead of your distro if the release lands before the vendor ships
- 3just find a timezone that matches, and move everything to it.
- 4Relying on version control systems like GitHub or Bitbucket
- 5Using sandboxes for testing changes
- 6Restricting user permissions
In their words
Unedited, most upvoted first, each linked to the thread it came from.
“I already changed it in Production.”source ↗
“Came into the office this morning and got an emergency meeting request that read "Daylight Savings Taskforce"”source ↗
“oh god that's gonna be a lot of patching, GPO, and Intune work with 1 months notice.”source ↗
““I just changed the field API names.””source ↗
““We went ahead and refreshed the Sandbox.””source ↗
“How do you manage DCIM/IPAM data in an IaC/GitOps-style workflow?”source ↗
“I'm especially interested in handling manual changes and drift, like when I introduce a new machine or change IP of existing machine - what happens next.”source ↗
“dealing with all the patching has been a mess. I can't imagine only 6 weeks notice.”source ↗
Where this came up
People with this problem also raised
- 9How to handle undocumented legacy database changes
- 2Manager changing my timesheet to add unpaid lunch breaks
- 4Why is keeping up with software updates so exhausting?
- 4Why is my gray kitten turning orange?
- 4How to find a new wedding dress tailor after yours closes
- 2Why do permission changes take so long to apply now?