-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Container App Revisions become unmanageable after updates (via API or portal) #19285
Comments
I am experiencing the same issues ☝️ when deploying updates to a containerapp using bicep and github actions. |
Is this on Microsoft's roadmap yet? As it is a new service with a lot of potential users migrating from Container Instances I think this deserves to be prioritised. |
Hi People, please there are any update? We want to use this feature but without the terraform module, we cannot start to use it. |
Same here. Is this isolated to certain users or how are others using it in production in this state? |
Hi all - Whilst this issue is still outstanding, we've worked together with the service team to establish a workaround to prevent this issue until such time as a long term solution can be found/implemented, so the initial support for this is now in final review stage for the provider in hashicorp/terraform-provider-azurerm#18008 |
There are multiple themes going on here. Just so there is no confusion
|
Container Apps Reports Timeout on LRO despite apparently actually deploying and starting the containers in the revision.
API Call returns:
The revision being “created” is the
rev4
noted displayed asProvisioned
, and the container is started successfully as shown in the App Insights log entry:However, the service reports
"provisioningState”: “Failed”
.The Update configuration (specifically a configuration containing the minimum required properties plus a revisionSuffix), when sent as a Create operation, works correctly. Additionally, if it is the first update to a newly created resource, it also works correctly. If applied as a subsequent update, it fails and the service cannot be updated further, even via the Portal, e.g.
API Version:
2022-03-01
The text was updated successfully, but these errors were encountered: