azurerm_cognitive_deployment rai_policy default is no longer the default

[rmcolbert]

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 comments along the lines of "+1", "me too" or "any updates", 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

1.14.4

AzureRM Provider Version

4.65.0

Affected Resource(s)/Data Source(s)

azurerm_cognitive_deployment

Terraform Configuration Files

resource "azurerm_cognitive_deployment" "example" {
  name                 = "example-cd"
  cognitive_account_id = azurerm_cognitive_account.example.id

  model {
    format  = "OpenAI"
    name    = "text-curie-001"
    version = "1"
  }

  sku {
    name = "Standard"
  }
}

Debug Output/Panic Output

# resource azurerm_cognitive_deployment.example will be updated in-place
~ resource "azurerm_cognitive_deployment" "example" {
    id              = <example>
    name            = "example-cd"
  - rai_policy_name = "Microsoft.DefaultV2" -> null
}

Expected Behaviour

Subsequent applies should show no changes

Actual Behaviour

rai_policy is being set to "Microsoft.DefaultV2" in Azure and Terraform wants to change it back to null.

Steps to Reproduce

Create a cognitive account with a kind of OpenAI or AIServices.
Deploy any model with minimal inputs (do not set rai_policy_name)
Run a plan and look for:

• rar_policy_name = "Microsoft.DefaultV2" -> null

Important Factoids

This only recently started happening, so I suspect Microsoft may have changed something on the ARM side to return the value as there are now Microsoft.Default and Microsoft.DefaultV2 policies.

References

No response

[promisinganuj]

Hi @rmcolbert, thanks for taking the time to report this issue. I can confirm the behaviour you’re seeing. As you suspected, it appears to be related to a change on the ARM side.

I’m currently gathering some additional information and will raise a PR to address this soon. In the meantime, you can use the ignore_changes option as a workaround in your configuration:

lifecycle {
  ignore_changes = [rai_policy_name]
}