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
ignore_all on tf 1.3.1 not working for azurerm_key_vault_key but is working in 1.3.0. #18653
Comments
@fardarter Thanks for opening this issue. Interesting, I can reproduce this issue on my side. I'll see what I can do for this issue. |
Thanks! |
@fardarter I've opened an issue on Terraform Core. I doubt the issue was introduced by this pr, will dig in. |
Appreciate the attention this is getting. I'll be honest, this is not my usual experience with MS maintenance, so thank you for being exceptional. |
@fardarter Apology for your inconvenience. I'll keep you updated if I get any progress. |
@fardarter I've made a mistake. Pr #31914 is meant to fix this issue. I confirm that this issue has been solved in Terraform v1.3.2. You can test it on your side, please let me know if you have any further question on this issue. Thanks. |
I'll test it out, thanks. I also spotted that PR and wondered, but 1.3.2 wasn't out last week. I'll say something if it doesn't resolve. |
Seems fine. Thanks for the help! |
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
1.3.1
AzureRM Provider Version
3.25.0
Affected Resource(s)/Data Source(s)
azurerm_key_vault_key
Terraform Configuration Files
Debug Output/Panic Output
Will provide if required under direction.
Expected Behaviour
There should be no changes to the resource as per
ignore_changes = all
Actual Behaviour
This is what I get in plan in 1.3.1. It does not appear in 1.3.0. (Note all secrets have been made useless and ids and urls replaced.)
Steps to Reproduce
terraform plan
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: