Chocolatey Central Management - Allow Secondary Statuses to indicate why there was a failure

[sync-by-unito]

Description

We have a customer who has the exitOnRebootDetected feature enabled in their environment, and when it triggers, the deployment is listed as "failed" in Chocolatey Central Management. The user has asked that if this happens, they would like to be able to receive a "cancelled" status or, even better, be able to create a custom status that could be generated when the exit code is triggered.

Why Is It Needed

This would be beneficial to expand reporting options within CCM to allow customers to understand where their deployments are failing.

Related Issues and Tickets

Zendesk ticket for reference

┆Issue is synchronized with this Gitlab issue by Unito

[pauby]

Thanks for raising this issue. After reviewing it, it's not something we expect to prioritise in the foreseeable future. We’re closing it to keep our backlog focused, but we’re open to revisiting it in the future if priorities shift or new interest arises. You are welcome to comment here or open a new issue if you'd like to discuss it further down the line.