-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Terraform plan with azurerm_dns_a_record fails when parsing existing dns record with azurerm 3.19.0 #18039
Comments
Same for CNAME record with provider version 3.19.0. |
Same here, this started being an issue in the new provider version v3.19.0 for us as well. |
I pushed a PR just now #18044 |
@domenicomastrangelo is there any workaround available until release of the fix? |
@hamza-tumturk you could downgrade the image to 3.18.0 as that seems to be working correctly |
Same with azurerm_dns_zone also:
|
Hey @abreunig359 Thanks for the report and thanks to @domenicomastrangelo for the quick PR! We appreciate everyone adding context and upvoting this. We'll have to review and test the PR to see if it fully solves the root cause of the bug, but we'll keep everyone here updated once that's figured out. As far as workarounds go, I recommend downgrading to 3.18.0 if this is affecting anyones environment. |
We've PR'd a fix in #18048 and will be rolling out a point release shortly. |
This is still happening for CNAME records:
|
This functionality has been released in v3.19.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
New issue opened here for v3.19.1 |
We are using azurerm version 3.23.0 and faced this issue while deleting an A record. I thought this has been fixed in version 3.19.1 and shouldn't be happening in the higher versions 🤔
|
Having this issue also with 3.23.0 |
Having this issue also with 3.24.0! |
Still seeing this issue with 3.25.0 |
We're having it with 3.26.0 as well |
Issue is fixed with 3.27.0. |
Just tried this and I'm still getting the same issue for CNAME with v 3.27.0 :'( |
@TommyBeaton if you're still seeing this in the most recent version of the provider you'll need to ensure the Resource ID being provided is in the correct format, the state migration will only fix existing resources upgrading to the new version - if the casing is defined incorrectly in the config you'll need to update this per the validation error message being returned. |
I'm just pulling the resource ID from a resource declared above it |
@TommyBeaton this issue's related to DNS Records, there isn't a field for Namespace ID in the DNS Resources, so this must be related to another resource? |
Sorry, that was related to another issue I had earlier today 😅 Will investigate now |
@tombuildsstuff - this worked for me, thank you! 🙏 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Is there an existing issue for this?
Community Note
Terraform Version
0.14.10
AzureRM Provider Version
3.19.0
Affected Resource(s)/Data Source(s)
azurerm_dns_a_record
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Terraform plan should finish successfully.
With azurerm 3.18.0 it works fine.
There where no changes to the dns config, aside from upgrading the provider version to 3.19.0
Actual Behaviour
Terraform plan fails with parsing error.
Steps to Reproduce
Run
terraform plan
orterraform apply
with an existing dns_a_record after upgrading to azurerm 3.19.0Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: