-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
azurerm_network_connection_monitor errors on cty.ObjectVal(map[string]cty.Value{"address":cty.StringVal("terraform.io") #22659
Comments
@esdccs1 does this happen during create or update?
For create scenario, could you check if there is multiple |
@myc2h6o all these resources were all created yesterday in a development environment. The error only appears intermittently, and after another deployment pipeline is fired off, it successfully plans, then applys.
Yes, in our configuration we are creating 3 connection_monitor resources that all use a single VM as their source endpoint, set to different destinations elsewhere on a network. The error shows up on all 3 , but it is the exact same error in the output. The bug shows up on updating the resource, I haven't seen it on creation yet. |
@esdccs1 while this might be an issue within the Terraform itself hashicorp/terraform-provider-aws#28191 (comment) (though unclear yet) While we doing further investigation, I'd suggest try with the latest Terraform version and see if it could resolve the issue |
We are using 3.78 azure provider and still getting this issue. Any update on the matter? When we run terraform apply it randomly fails on these connection monitors resources. here is a sample resource block... could it be it doesn't like the "-" character in the url address field?
|
Is there an existing issue for this?
Community Note
Terraform Version
1.3.9
AzureRM Provider Version
3.66
Affected Resource(s)/Data Source(s)
azurerm_network_connection_monitor
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
no error messages telling me to submit a bug report.
Actual Behaviour
No response
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: