You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using a local variable list/map to add Vlans to a Ethernet Network Group Policy .
(intersight_fabric_eth_network_group_policy).
This source local variable list/map is also used to create multiple other resources (ACI vlans, ACI Static ports, Kubernetes NetworkAttachementDefinitions.
Using join/tolist to create the strings of Vlans that needs to be added.
Vlans will therefore not contain ranges (eg: 180,1140,1141)
Because Intersight automatically changes these to ranges when it can, Terraform always reports a change and wants to re-apply a change after every run, even if zero change applied to repo.
Is it possible to add some smarts to the Intersight provider to correlate ranges vs list of vlans?
Thanks.
Terraform-provider-intersight version
Terraform v1.8.3
Using previously-installed hashicorp/kubernetes v2.33.0
Using previously-installed ciscodevnet/intersight v1.0.58
Using previously-installed ciscodevnet/aci v2.15.0
Description
We are using a local variable list/map to add Vlans to a Ethernet Network Group Policy .
(intersight_fabric_eth_network_group_policy).
This source local variable list/map is also used to create multiple other resources (ACI vlans, ACI Static ports, Kubernetes NetworkAttachementDefinitions.
Using join/tolist to create the strings of Vlans that needs to be added.
Vlans will therefore not contain ranges (eg: 180,1140,1141)
Because Intersight automatically changes these to ranges when it can, Terraform always reports a change and wants to re-apply a change after every run, even if zero change applied to repo.
Is it possible to add some smarts to the Intersight provider to correlate ranges vs list of vlans?
Thanks.
Terraform-provider-intersight version
Terraform v1.8.3
Configuration file
Actual output (Attach screenshots if applicable)
Related issues/PRs
none
Suggest a fix
none
The text was updated successfully, but these errors were encountered: