Azure / Azure/bicep-registry-modules

[AVM Module Issue]: Container Apps Environment enters failed state after enabling .NET Development Stack and running subsequent deployment

Open
#7,129 8 comments 1 reaction 1 assignee Claimed by @oZakari View on GitHub
Class: Resource Module :package: Needs: Immediate Attention :bangbang: Needs: Triage :mag: Status: Response Overdue :triangular_flag_on_post: Type: AVM :a: :v: :m: Type: Bug :bug:
Dominant language
Bicep
Stars
736
Forks
564
Avg merge
3d 15h
Merged PRs (30d)
30

Description

### Check for previous/existing GitHub issues

- [x] I have checked for previous/existing GitHub issues

### Issue Type?

Bug

### Module Name

avm/res/app/container-app

### (Optional) Module Version

_No response_

### Description

After enabling the .NET Development Stack on a Container App via the Azure Portal, subsequent deployments using the AVM module fail, and the associated Container Apps Managed Environment transitions to a failed provisioning state.

```
"details": [
{
"code": "OperationFailed",
"message": "Update environment AKS handler failed: 'R' is an invalid start of a value. Path: $ | LineNumber: 0 | BytePositionInLine: 0.."
}
]
```

### (Optional) Correlation Id

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.