search

microsoft / azure-container-apps

Roadmap and issues for Azure Container Apps
MIT License
372 stars 29 forks source link

Feature Request: Warning status in execution history #1247

Closed DupuyNicolas closed 2 months ago

DupuyNicolas commented 3 months ago

Is your feature request related to a problem? Please describe.
The jobs i run in my Azure Container App Jobs, can sometimes throw warnings, which are not critical for the job to run but need further investigations. I would like to see that without having to go in the log analytics for each execution.

Describe the solution you'd like.
I would like to have another status (in addition to succes, error, and cancelled) in the execution history which would be "ended with warning", or "degraded" (yellow in UI). Executions exiting with code 1 for example or another specific code could trigger this status. Also we could imagine having a warningTimeout which would trigger the degraded state if the job takes longer than specified to execute, but would not kill it.

Describe alternatives you've considered.
For the moment i treat warnings as success.

anthonychu commented 2 months ago

@DupuyNicolas Executions with non-zero exit codes are considered errors and will cause the execution to fail (or retry if configured).

Besides jobs taking longer than expected, can you share more info about what else you consider as warnings?

microsoft-github-policy-service[bot] commented 2 months ago

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.