Using Container App Environment with Consumption Workload Profile shows drift in plan

[krusty93]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

When creating a Container App Environment with Consumption only Workload Profiles, the provider wants to replace the workload_profile block at every plan/apply.

The issue can be work around by using ignore_changes:

  lifecycle {
    ignore_changes = [
      workload_profile,
    ]
  }

• 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.13.1

AzureRM Provider Version

4.61.0

Affected Resource(s)/Data Source(s)

azurerm_container_app_environment

Terraform Configuration Files

resource "azurerm_container_app_environment" "example" {
  name                = var.name
  resource_group_name = var.resource_group_name
  location            = var.location

  identity { type = "SystemAssigned" }

  infrastructure_subnet_id       = var.subnet_id
  internal_load_balancer_enabled = false
  public_network_access          = "Disabled"

  log_analytics_workspace_id = var.log_analytics_workspace_id
  zone_redundancy_enabled    = false

  workload_profile {
    maximum_count         = 1
    minimum_count         = 1
    name                  = "Consumption"
    workload_profile_type = "Consumption"
  }

  tags = var.tags
}

Debug Output/Panic Output

# azurerm_container_app_environment.example will be updated in-place
  ~ resource "azurerm_container_app_environment" "example" {
        id                                          = "redacted"
        name                                        = "redacted"
        tags                                        = {
            "redacted"     = "redacted"
        }
        # (17 unchanged attributes hidden)

      - workload_profile {
          - maximum_count         = 0 -> null
          - minimum_count         = 0 -> null
          - name                  = "Consumption" -> null
          - workload_profile_type = "Consumption" -> null
        }
      + workload_profile {
          + maximum_count         = 1
          + minimum_count         = 1
          + name                  = "Consumption"
          + workload_profile_type = "Consumption"
        }

        # (1 unchanged block hidden)
    }

Expected Behaviour

No changes

Actual Behaviour

The resource azurerm_container_app_environment shows a drift

Steps to Reproduce

1. terraform apply
2. terraform plan

Important Factoids

No response

References

No response

[rcskosir]

This looks related to PR #30139 (released in v4.37.0). Since you're on v4.61.0, the fix should be included, but the drift may still occur because of how you've configured the Consumption profile.

For Consumption workload profiles, can you try not specifying minimum_count or maximum_count. The Azure API ignores these values and always returns 0, causing the drift you're seeing. Try updating your configuration to:

workload_profile {
  name                  = "Consumption"
  workload_profile_type = "Consumption"
  # Do NOT include minimum_count or maximum_count
}

Only non-Consumption profiles (D4, E4, etc.) should include the count fields. The provider's handling explicitly omits these values for Consumption types, and the diff suppression logic expects them to not be present in your config.

[krusty93]

Thank you @rcskosir for your feedback. I confirm that by removing them the drift is not there anymore

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