azurerm_role_assignment would be planed to replace

[Shabahang]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

1.4.5

AzureRM Provider Version

3.61.0

Affected Resource(s)/Data Source(s)

azurerm_role_assignment

Terraform Configuration Files

when with version 3.61.0 and 3.62.0 , the object azurerm_role_assignment will be planed to replace , while it is not the case on 3.58.0.

   # azurerm_role_assignment.<.....> must be replaced
-/+ resource "azurerm_role_assignment" "<.....>" {
...
...
~ principal_id = "......." -> "........." # forces replacement

Plan: 1 to add, 0 to change, 1 to destroy.

Debug Output/Panic Output

# azurerm_role_assignment.<.....> must be replaced
-/+ resource "azurerm_role_assignment" "<.....>" {
...
...
~ principal_id = "......." -> "........." # forces replacement

Plan: 1 to add, 0 to change, 1 to destroy.

Expected Behaviour

It should bot be planed to replacement, and it was not in 3.58.0

Actual Behaviour

No response

Steps to Reproduce

No response

Important Factoids

No response

References

No response

[rcskosir]

Thanks for taking the time to submit this issue. Unfortunately, it looks like the configuration you provided is missing some key pieces that we don’t want to make assumptions about. Please update this issue with a more complete configuration of the azurerm_role_assignment so that we are able to work on reproducing this.

[rcskosir]

Thanks for taking the time to submit this issue. Unfortunately we aren’t able to investigate this without the relevant portions of your Terraform configuration file(s). We are going to close this issue - if you are able to provide us with additional information we may reopen this.

[github-actions]

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.