Check if object relationship creation or update failure is not silent. (DCNE-82)

[lhercot]

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

Terraform Version

APIC version and APIC Platform

• V x.x.x and on-prem/cloud-aws/cloud-azure/all.

Affected Resource(s)

• check all resources

Expected Behavior

When an error happens and APIC reject the POST related to a relationship or other child object from a resources. Terraform provider should fail with clear error message.

Actual Behavior

Unknown. This is why we need to check.

References

See #791 for context and an example.

[JC1231231]

We were running aci provider at 2.6.1 there was no issue. and after upgraded to 2.7 we noticed that terraform is trying to remove and add back the same configuration though there is no change in codes. Suspected this is related to this issue or an update in the "encap" feature introduced in 2.7. Rollback to 2.6.1 this was fixed anyway

aci_l3out_floating_svi.floating_svis12[“L3out-vrf”] will be updated in-place

~ resource “aci_l3out_floating_svi” “floating_svis12” {
id
# (15 unchanged attributes hidden)
+ relation_l3ext_rs_dyn_path_att {
+ floating_address = “”
+ forged_transmit = “Disabled”
+ mac_change = “Disabled”
+ promiscuous_mode = “Disabled”
+ tdn = “uni/phys-Phys-dom”
}
- relation_l3ext_rs_dyn_path_att {
- encap = “unknown” -> null
- floating_address = “” -> null
- forged_transmit = “Disabled” -> null
- mac_change = “Disabled” -> null
- promiscuous_mode = “Disabled” -> null
- tdn = “uni/phys-Phys-dom” -> null
}
}