azure container app environment rg name cant be specified

[jnzo999]

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

AzureRM Provider Version

3.41

Affected Resource(s)/Data Source(s)

azurerm_container_app_environment

Terraform Configuration Files

resource "azurerm_container_app_environment" "acae" {
    name                       = var.acae_name
    location                   = "northeurope"
    resource_group_name        = var.rg
    log_analytics_workspace_id = var.workspace_id
    infrastructure_resource_group_name = var.infrastructure_rg_name         //creates new rg with load balancer with internal ip from the subnet range
    infrastructure_subnet_id = var.infrastructure_subnet_id
    internal_load_balancer_enabled = true
    workload_profile {
        name = var.workload_profile_name
        workload_profile_type = var.workload_profile_type 
        maximum_count = var.workload_maximum_count
        minimum_count = var.workload_minimum_count
    }
    
}

Debug Output/Panic Output

infrastructure_resource_group_name 
 = 
ME_<container app environment name>_<container app rg>_northeurope


// 
in the documentation it says that we need to specify a workload profile to enable choosing a specific name - not working

Expected Behaviour

infrastructure_resource_group_name will get the name we give it (<var.infrastructure_rg_name>)

Actual Behaviour

generating a default value for the infrastructure_resource_group_name

Steps to Reproduce

No response

Important Factoids

No response

References

No response

[jiaweitao001]

Hi @jnzo999 , this is related to the issue reported here #26777