`import` cannot evaluate resources which require state upgrades

[casstait]

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 (and AzureRM Provider) 3.0.1

Affected Resource(s)

• azurerm_mssql_database

Terraform Configuration Files

resource "azurerm_mssql_database" "mssql_database" {
name = "tentaclearmy-mssql-database-${lower(var.environment)}"
server_id = azurerm_mssql_server.mssql_server.id
max_size_gb = 2
sku_name = "Basic"
}

Expected Behaviour

terraform plan or import should succeed

Actual Behaviour

Receive the following error:

Error: Invalid resource instance data in state
│
│   on /Users/.../Octopus/TentacleArmy/terraform/main.tf line 71:
│   71: resource "azurerm_mssql_server" "mssql_server" {
│
│ Instance azurerm_mssql_server.mssql_server data could not be decoded from the state: unsupported attribute "extended_auditing_policy".

Steps to Reproduce

in main.tf

resource "azurerm_mssql_database" "mssql_database" {
  name             = "tentaclearmy-mssql-database-${lower(var.environment)}"
  server_id       = azurerm_mssql_server.mssql_server.id
  max_size_gb = 2
  sku_name      = "Basic"
}

1. terraform import azurerm_mssql_database.example /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/group1/providers/Microsoft.Sql/servers/server1/databases/example1

Important Factoids

AzureRM recently updated a major version to 3.0

[mbfrahry]

Hey @casstait, I've been trying a number of ways to recreate this issue but haven't been able to. Could you share a bit more on how you got to the issue you're seeing? What version of Azure were you upgrading from and do you have a way to consistently reproduce this issue that you could share?

[katbyte]

Also if this continues to be an issue casstait a copy of the debug lo with TF_LOG=TRACE terraform import would be very helpful!

[jbardin]

Hi @casstait,

Thanks for filing the issue! This appears to be a result of the rather limited context within which import operates, which means it's not able to upgrade existing state to match a new provider version. The workaround here should be to complete an apply operation first to ensure the existing resources are refreshed and upgraded to the new provider version.

[casstait]

@jbardin The apply produced the same error. The workaround for us was to just manually manipulate the state until it was in the desired outcome.

Maybe the provider code could be a bit clever and notice what schema version a resource is using and then if the provider version doesn't match that it can update the state of a resource when these kind of things happen. I understand that's a big ask and out of scope for this issue but just a forwarding suggsetion.