Add support to import L4-L7 Service Device from other tenant (DCNE-513)

[hpalm242]

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 ACI 2.17 provider lacks the functionality to import a L4-L7 Service Device from another tenant.

Need to create the following object in the importing tenant
{
"vnsLDevIf": {
"attributes": {
"dn": "uni/tn-[Importing tenant name]/lDevIf-[uni/tn-[Exporting tenant]/lDevVip-[Service Device Name]]",
"ldev": "uni/tn-[Exporting tenant]/lDevVip-[Service Device Name]",
"rn": "lDevIf-[uni/tn-[Exporting tenant]/lDevVip-[Service Device Name]]"
},
"children": []
}
}

APIC version and APIC Platform

• ACI 5.2.1g on-prem

[shrsr]

@hpalm242 Thank you for opening the issue.

I believe you can use a device from another tenant using the attribute relation_vns_rs_l_dev_ctx_to_l_dev in the resource aci_logical_device_context. Can you please let us know if this works for you?

Example:

resource "aci_logical_device_context" "example" {
  tenant_dn         = aci_tenant.importing_tenant.id
  ctrct_name_or_lbl = "default"
  graph_name_or_lbl = "any"
  node_name_or_lbl  = "any"
  annotation        = "example"
  description       = "from terraform"
  context           = "ctx1"
  name_alias        = "example"
  relation_vns_rs_l_dev_ctx_to_l_dev = "uni/tn-exporting_tenant/lDevVip-service_device_name"
}

For more details, please go through:
https://registry.terraform.io/providers/CiscoDevNet/aci/latest/docs/resources/logical_device_context

[hpalm242]

Thank you @shrsr,

but as far as I can see and from my tests aci_logical_device_context creates a Device Selection Policy, vnsLDevCtx. For the Device Selection Policy to work with a L4-L7 Device from another tenant a vnsLDevIf is required.

[shrsr]

@hpalm242 Our team will look into this and address it appropriately.

[hpalm242]

Thank you @shrsr!