Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Container App Environments - Add "consumption" option for workload profile #24608

Closed
1 task done
admsallai opened this issue Jan 23, 2024 · 2 comments · Fixed by #25285
Closed
1 task done

Azure Container App Environments - Add "consumption" option for workload profile #24608

admsallai opened this issue Jan 23, 2024 · 2 comments · Fixed by #25285

Comments

@admsallai
Copy link

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.

Description

By default when NOT providing "workload_profile" block, terraform is creating consumption only environment type.

When "workload_profile" block is provided there is no option to only use default consumption profile since one of D4, D8, D16, D32, E4, E8, E16 and E32 is required.

There is no option to create workload profiles environment type only with defaulty created consumption profile, so following manual in portal setup is not possible with terraform:
Screenshot 2024-01-23 172936

New or Affected Resource(s)/Data Source(s)

azurerm_container_app_environment

Potential Terraform Configuration

resource "azurerm_container_app_environment" "agent_con_app_env" {
  name                           = "environment-name"
  location                       = "location"
  resource_group_name            = "rg-name"
  log_analytics_workspace_id     = azurerm_log_analytics_workspace.log_analytics.id
  infrastructure_subnet_id       = azurerm_subnet.infra_subnet
  internal_load_balancer_enabled = true

   workload_profile {
    name                  = "workload-name"
    workload_profile_type = "Consumption" #or ability to skip this since consumption profile is default
    maximum_count         = 5
    minimum_count         = 1
  }
}

References

No response

@jaromirmikulik
Copy link

The Example configuration for Consumption workload profile could look like this:


resource "azurerm_container_app_environment" "agent_con_app_env" {
  name                           = "environment-name"
  location                       = "location"
  resource_group_name            = "rg-name"
  log_analytics_workspace_id     = azurerm_log_analytics_workspace.log_analytics.id
  infrastructure_subnet_id       = azurerm_subnet.infra_subnet
  internal_load_balancer_enabled = true

   workload_profile {
    workload_profile_type = "Consumption" #or ability to skip this since consumption profile is default
  }
}

"Consumption" workload profile type doesn't have any other values need to fill in.

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.