Replies: 2 comments
|
Thanks for taking the time to raise this and for sharing your use case. You’re right that these ACI object types are currently not modeled in the plugin. There isn’t a committed timeline for adding them yet, but they are valid areas to consider for future model coverage. For broader questions like this, I’ve enabled GitHub Discussions. Since this request spans several separate areas of the ACI policy model, I’m going to convert this issue into a discussion so it can be used as a roadmap/design conversation rather than one very large feature request. Once the scope is clearer, I’d prefer to split this into smaller implementation issues with concrete model definitions, relationships, and acceptance criteria. Details about which objects and relationships you need for Terraform provisioning would be very helpful. |
|
@ahusking Thanks again for helping highlight these gaps. Since your original post, I’ve been working through much of the requested model coverage, and a large part of it is now included in v0.4.0. I hope it will be useful to your team and to others using the plugin. I believe the main remaining areas from your list are L2Out and routing support. Could you share a little more about the specific functionality and relationships your team needs, particularly for Terraform provisioning? It would also be helpful to know which area is more important to you. |
Uh oh!
There was an error while loading. Please reload this page.
NetBox ACI Plugin version
0.2.1
NetBox version
v4.5.9
Feature type
Data model extension
Proposed functionality
We've been looking at building out ACI using this, and one of my ACI guys have noticed that we're missing the following object types, is there a plan to add them?
L2out
L3out
routing (static + dynamic)
domains
vlan pools
AAEP
Thanks
Use case
With these objects in netbox we plan to use them to provision terraform
External dependencies
No response
All reactions