Skip to content
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

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

Open
sync-by-unito bot opened this issue Jan 26, 2024 · 0 comments
Labels
0 - _Triaging New tickets that need to be hashed out a bit more before they hit the backlog. CentralManagement Issues affecting Central Management

Comments

@sync-by-unito
Copy link

sync-by-unito bot commented Jan 26, 2024

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

@sync-by-unito sync-by-unito bot added 0 - _Triaging New tickets that need to be hashed out a bit more before they hit the backlog. CentralManagement Issues affecting Central Management labels Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - _Triaging New tickets that need to be hashed out a bit more before they hit the backlog. CentralManagement Issues affecting Central Management
Projects
None yet
Development

No branches or pull requests

0 participants