3 ms·
I fundamentally disagree. The source of truth should be naively updating my components, not a script that may or may not break with the next update which has 0
by tw04 3y ago
I fundamentally disagree. The source of truth should be naively updating my components, not a script that may or may not break with the next update which has 0 support available.
Given the repeated asks on the GitHub issues, I’m confident I’m not alone in that belief.
Infoblox doesn’t tell me to write a terraform script to update AD/dns and vice versa, they built it into the product.
- SteveNuts 3y agoNetbox isn't really a DHCP/DNS server and doesn't claim to be. You don't have to use its IPAM features if you want to use Infoblox instead. Netbox has a lot of great features for documenting your infrastructure even if you don't use IPAM - which Infoblox does not do at all.
- tw04 3y agoI understand what it currently does. I’m saying they’re missing the mark and should finish building out the tool. I don’t want a separate tool for each.
- jeffg-nbl 3y agoOur current focus, with our current resources, is on core functionality. We want to nail that and then grow our roadmap deliberately, rather than go off and add a bunch of half-finished features just to tick some checkboxes. In the meantime, plugin builders are doing an amazing job tackling things like BGP community / session / policy management, DNS record management, and device ACL management.