You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Terraform is becoming more and more popular thanks to it's state management, moreover we now have the nice OpenTofu fork out due to license change.
A nice netbox TF provider is avaible at GitHub
The documentation is on TF registry
I think it should become official, and support it in both directions (as a data source FROM netbox, and also as a ressource manager to push to netbox).
Additionally, in a later roadmap there could be a generator to create the Go code for the provider based upon the NetBox plugins you have. It's always the same and depend on the schema for each type of object.
There could also have direct support for the most common plugins in the release, such as BGP,
Here are the reasons I think it would be nice to have
Vendors like Cisco or Fortigate are making complete and efficient TF providers, letting now you manage your network just like you would do with a AWS VPC. Thus simply because more and more customer asks for TF support, as it's most of the time one of the cleanest ways to maintain config and dependencies.
Terraform/OpenToFu could become an easy to move data IN and OUT, without needing plugins. e.g import FW ACL, Cisco ACI config, Wireless AP infos and so on
This would help entreprises that got stuff on cloud providers to exchange with NetBox
80% of the job might be done thanks to the already existing TF provider
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
Terraform is becoming more and more popular thanks to it's state management, moreover we now have the nice OpenTofu fork out due to license change.
A nice netbox TF provider is avaible at GitHub
The documentation is on TF registry
I think it should become official, and support it in both directions (as a data source FROM netbox, and also as a ressource manager to push to netbox).
Additionally, in a later roadmap there could be a generator to create the Go code for the provider based upon the NetBox plugins you have. It's always the same and depend on the schema for each type of object.
There could also have direct support for the most common plugins in the release, such as BGP,
Here are the reasons I think it would be nice to have
Beta Was this translation helpful? Give feedback.
All reactions