Add support for L3Out Templates (DCNE-48)

[andbyrne]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Add a resource and data source to manage L3Out templates.

There are two objects that can be defined under a L3Out template. Each of these will also require a corresponding resource and data source:

• L3Out
• SR-MPLS VRF L3Out

NDO version

• V 4.1+

References

https://www.cisco.com/c/en/us/td/docs/dcn/ndo/4x/configuration/cisco-nexus-dashboard-orchestrator-configuration-guide-aci-411/ndo-configuration-aci-use-case-l3out-411-41x.html

[lhercot]

Hi @andbyrne ,

Thanks for opening this enhancement request.

FYI, the current API for the L3Out templates does not allow us to modify single policies individually.
We are working with the NDO API team to resolve this issue and will only be able to create dedicated resources once this is addressed.

[paul4cooper]

When will the NDO Data Model be updated for the separate L3 Out and Tenant Polices Templates?

We are running version 4.2.1d and utilising terraform/yaml files to create new transit L3Out and would like to fully automate the process but current NDO Model does not include these new templates.

https://developer.cisco.com/docs/nexus-as-code/#!ndo

[lhercot]

Hi Paul, we first need to support it in the provider and then add it to Nexus as Code model.

We are currently working with the NDO API team as we are testing some new APIs they have developed for this use case.
Once we have more details, we will update here.

[asmith432]

Has there been any progress on this issue?

[akinross]

Hi @asmith432, no not yet. Issue will be updated when there is progress made.