vRealize Automation can have multiple networks being attached to the same ip range. This is necessary if you have multiple DVSwitches / Network Domains in your Datacenter with different portgroups of the same VLAN.
The Terraform argument vra_network_ip_range.fabric_network_id is limited to a single value which does not reflect the reality.
I request you to change the Type from String to List.
Describe alternatives you've considered
To keep backward compatibility it would make sense to add another argument and mark fabric_network_id as deprecated.
References
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
Code of Conduct
This project has a Code of Conduct that all participants are expected to understand and follow:
Description
vRealize Automation can have multiple networks being attached to the same ip range. This is necessary if you have multiple DVSwitches / Network Domains in your Datacenter with different portgroups of the same VLAN. The Terraform argument vra_network_ip_range.fabric_network_id is limited to a single value which does not reflect the reality. I request you to change the Type from String to List.
Describe alternatives you've considered
To keep backward compatibility it would make sense to add another argument and mark fabric_network_id as deprecated.
References
Community Note