Closed bryansan-msft closed 3 months ago
Reviewing the azurerm provider, the subresource_name
property within the ip_configuration
block is a string.
The subresource_names
property within the private_service_connection
is a list(string)
.
It looks like the module reuses the same variable for both, hence why we are seeing an error.
[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.
[!TIP]
- To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
- To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!
[!NOTE] This message was posted as per ITA01TF.
[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.
[!TIP]
- To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
- To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!
[!NOTE] This message was posted as per ITA01TF.
[!CAUTION] This issue requires the AVM Core Team's (@Azure/avm-core-team-technical-terraform) immediate attention as it hasn't been responded to within 6 business days.
[!TIP]
- To avoid this rule being (re)triggered, the "Needs: Triage :mag:" and "Status: Response Overdue :triangular_flag_on_post:" labels must be removed when the issue is first responded to!
- Remove the "Needs: Immediate Attention :bangbang:" label once the issue has been responded to.
[!NOTE] This message was posted as per ITA02TF.
It seems it was magically fixed as it is not possible to reproduce as per today
Is there an existing issue for this?
Greenfield/Brownfield provisioning
greenfield
Terraform Version
1.7.5
Module Version
0.1.1
AzureRM Provider Version
3.102.0
Affected Resource(s)/Data Source(s)
azurerm_private_endpoint
Terraform Configuration Files
tfvars variables values
Debug Output/Panic Output
Expected Behaviour
Deploy correctly the storage account with static ips
Actual Behaviour
Run just fails
Steps to Reproduce
just terraform apply. The code I used to reproduce the issue is the same you have in your examples for private-endpoint
Important Factoids
Nothing
References
Nothing at all