EPG to Static AAEP Assignment (DCNE-581)

[DerrickTJ]

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

ACI Version 6.1 allowed for static AAEP assignments within the EPG now. Would be great to get that added here.

dn: uni/tn-derrick-lab/ap-ap1/epg-epg1/rsaepAtt-lab-aaep

Post example with just VLAN44, trunk and on-demand seem to be default:
method: POST
url: https://apic1.com/api/node/mo/uni/tn-derrick-lab/ap-ap1/epg-epg1.json
payload{"fvRsAepAtt":{"attributes":{"tnInfraAttEntityPName":"lab-aaep","encap":"vlan-44","status":"created"},"children":[]}}
response: {"totalCount":"0","imdata":[]}

Another example with VLAN44 and access port, and immediate:
url: https://apic1.com/api/node/mo/uni/tn-derrick-lab/ap-ap1/epg-epg1.json
payload{"fvRsAepAtt":{"attributes":{"tnInfraAttEntityPName":"lab-aaep","encap":"vlan-44","instrImedcy":"immediate","mode":"untagged","status":"created"},"children":[]}}
response: {"totalCount":"0","imdata":[]}

APIC version and APIC Platform

• V 6.1

Potential Terraform Configuration

I would expect this to be similar to aci_epg_to_domain

resource "aci_epg_to_static_aaep" "this" {
  application_epg_dn = "" # required
  aaep_name = "" # required 
  encap = "" # required? GUI will allow optional though I guess.
  primaryEncap = "" #optional, default null 
  mode = "" # optional, default trunk
 immediacy = "" # optional, default lazy
 
}

References

• #0000

[DerrickTJ]

Rest module for those that want to use this for the time being:

resource "aci_rest" "epg_to_static_aaep" {
  path = "api/node/mo/uni/tn-derrick-lab/ap-ap1/epg-epg1.json"
  payload = jsonencode({
    fvRsAepAtt : {
      attributes : {
        tnInfraAttEntityPName: "lab-aaep",
        encap: "vlan-44",
        primaryEncap: "",
        instrImedcy: "immediate",
        mode: "untagged",
      },
    }
  })
}

[akinross]

Hi @DerrickTJ, I have added the item to the backlog. In cas you want to manage individual attributes separately you could leverage: https://registry.terraform.io/providers/CiscoDevNet/aci/latest/docs/resources/rest_managed

[DerrickTJ]

Hi @DerrickTJ, I have added the item to the backlog. In cas you want to manage individual attributes separately you could leverage: https://registry.terraform.io/providers/CiscoDevNet/aci/latest/docs/resources/rest_managed

Yep, that is my plan for now. I put a note just above your that actually calls that out too.

[akinross]

Hi @DerrickTJ, I saw your note/comment and that refers to the https://registry.terraform.io/providers/CiscoDevNet/aci/latest/docs/resources/rest resource, and not the https://registry.terraform.io/providers/CiscoDevNet/aci/latest/docs/resources/rest_managed resource. The difference between them is that in your example the aci_rest manages the entire payload as a single string input. The other resource manages each attribute individually. Furthermore the aci_rest resource has not been migrated to terraform plugin framework, thus will lack some of the additional capabilities these new style resources are providing.

[DerrickTJ]

Oh I see! That's good to know, thanks!