Open fgarcia-cnb opened 6 months ago
Thanks for raising this issue. Maybe adding "depends_on = [azurerm_monitor_private_link_scoped_service.ampls_svc]" in "azurerm_private_endpoint" and then recreating them is helpful.
nah, won't make a difference since the scope service doesnt present any new changes, and it doesnt detect the dns changes in the private endpoint
Is there an existing issue for this?
Community Note
Terraform Version
1.0.7
AzureRM Provider Version
3.98.0
Affected Resource(s)/Data Source(s)
azurerm_monitor_private_link_scope, azurerm_monitor_private_link_scoped_service, azurerm_private_endpoint
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
all resources are created fine... but the 3rd resource (azurerm_monitor_private_link_scoped_service) causes changes to the "custom_dns_configs" attribute of the private endpoint. however, terraform does not bring these changes into state... instead it detects them in the "Objects have changed outside of Terraform" part of the run.
Actual Behaviour
How can we get the private endpoint to see the additional custom dns entries created by azurerm_monitor_private_link_scoped_service?
Steps to Reproduce
No response
Important Factoids
No response
References
No response