You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying Container Apps in Azure, it is common for the Container Apps Environment and the Container App itself to reside in separate resource groups (e.g., the environment Dev-Environment in Resource Group A and the app MyContainerApp in Resource Group B). However, when using the AzureContainerApps@1 task in an Azure DevOps pipeline, specifying different resource groups for the environment and the app leads to an error, as the task expects both resources to be in the same group.
Steps to Reproduce
Configure a pipeline with the AzureContainerApps@1 task:
Current Behavior
The deployment fails with the following error:
(ResourceNotFound) The Resource 'Microsoft.App/managedEnvironments/Dev-Environment' under resource group 'Resource Group B' was not found.
Expected Behavior
It should be possible to specify a different resource group for the Container Apps Environment using a full resource ID path, allowing for more flexible resource configurations.
Proposed Solution
Enable support for specifying a full resource ID for the containerAppEnvironment input in the AzureContainerApps@1 task, like:
containerAppEnvironment: '/subscriptions/12345678-1234-1234-1234-123456789012/resourceGroups/Resource Group A/providers/Microsoft.App/managedEnvironments/Dev-Environment'
Full Example Task
Here is an example of the full task configuration with the proposed solution:
Task name
AzureContainerApps@1
Describe your feature request here
Description
When deploying Container Apps in Azure, it is common for the Container Apps Environment and the Container App itself to reside in separate resource groups (e.g., the environment Dev-Environment in Resource Group A and the app MyContainerApp in Resource Group B). However, when using the
AzureContainerApps@1
task in an Azure DevOps pipeline, specifying different resource groups for the environment and the app leads to an error, as the task expects both resources to be in the same group.Steps to Reproduce
AzureContainerApps@1
task:Current Behavior
The deployment fails with the following error:
Expected Behavior
It should be possible to specify a different resource group for the Container Apps Environment using a full resource ID path, allowing for more flexible resource configurations.
Proposed Solution
Enable support for specifying a full resource ID for the
containerAppEnvironment
input in theAzureContainerApps@1
task, like:Full Example Task
Here is an example of the full task configuration with the proposed solution:
The text was updated successfully, but these errors were encountered: