Skip to content

Support for name in aci_l3_ext_subnet (DCNE-400) #1340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dirkf98 opened this issue Apr 28, 2025 · 1 comment
Open

Support for name in aci_l3_ext_subnet (DCNE-400) #1340

dirkf98 opened this issue Apr 28, 2025 · 1 comment
Labels
enhancement jira-sync Sync this issue to Jira

Comments

@dirkf98
Copy link

dirkf98 commented Apr 28, 2025

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

The resource aci_l3_ext_subnet does not support the attribute name. In newer ACI version, apparently starting from 5.2(7g) the name for a subnet entry can be configured in the GUI and can be used for some description for this configuration. In 5.2(7f) the attribute name is visible in Visore, but not on the APIC GUI.
It would be nice to have support for the attribute name in the Terraform resource for consistency.

New or Affected Resource(s) + ACI Class(es):

  • aci_l3_ext_subnet

APIC version and APIC Platform

  • V 5.2(7g) and on-prem

Potential Terraform Configuration

Add attribute name to the resource.

References

  • #0000
@akinross akinross added the jira-sync Sync this issue to Jira label Apr 28, 2025
@github-actions github-actions bot changed the title Support for name in aci_l3_ext_subnet Support for name in aci_l3_ext_subnet (DCNE-400) Apr 28, 2025
@akinross
Copy link
Collaborator

Hi @dirkf98, thank you for making us aware. I have added it to the backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement jira-sync Sync this issue to Jira
Projects
None yet
Development

No branches or pull requests

2 participants