Recreation of imported azurerm_security_center_setting for Serntinel

[oleksandr-ivanov-ah]

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 and review the contribution guide to help.

Terraform Version

v1.5.7

AzureRM Provider Version

3.84

Affected Resource(s)/Data Source(s)

azurerm_security_center_setting

Terraform Configuration Files

resource "azurerm_security_center_setting" "self" {
  setting_name = "SENTINEL"
  enabled      = true
}

Debug Output/Panic Output

# module.security-center.module.sentinel.azurerm_security_center_setting.self must be replaced
-/+ resource "azurerm_security_center_setting" "self" {
      ~ id           = "/subscriptions/00000000-0000-0000-0000-000000000000/providers/Microsoft.Security/settings/Sentinel" -> (known after apply)
      ~ setting_name = "Sentinel" -> "SENTINEL" # forces replacement
        # (1 unchanged attribute hidden)
    }

Expected Behaviour

setting_name argument for azurerm_security_center_setting have to be "Sentinel" instead of "SENTINEL"

Actual Behaviour

setting_name accepts only "SENTINEL" as a result existing (imported) azurerm_security_center_setting will be recreated.
According to the azure-rest-api-specs SettingName for Sentinel have to be "Sentinel"
I checked the initial version of azurerm_security_center_setting and it had correct setting_name value "Sentinel"

Steps to Reproduce

1. az security setting update -n "Sentinel" --enabled true
2. Import existing Sentinel azurerm_security_center_setting
3. Run terraform plan

Important Factoids

No response

References

No response

[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.