Changing Your IPAM Should Not Rewrite Every Deployment
Suppose a network team moves authoritative IPAM data from NetBox to Nautobot.
The deployment still needs the same thing it needed yesterday: trusted prefix and inventory data before it creates infrastructure. Yet operation definitions across the environment now need editing because they all say requires_authority: netbox.
That migration should alter one binding. Instead, it has spread into unrelated consumers.
The operation depends on an authority capability, while the environment decides which product supplies it. When both decisions occupy the same field, a product choice becomes part of every consumer's contract.
Disclosure: The implementation examples in this article come from HybridOps Core, which I maintain. I have no affiliation with NetBox or Nautobot.
Start With the Requirement
NetBox describes a network source of truth as the data foundation that tells automation what assets are in scope and what intended network state should be. Nautobot describes itselfas a network source of...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
