Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
COmanage Registry 0.8 (Omnipotent Octagon)
-
None
Description
When ProvisionerBehavior fires off provisioning plugins, there is currently no way to obtain failure status (other than a broad true/false) from afterSave() or other functions. This means it's not possible to report to the user that provisioning of a specific module failed. (As a workaround, a user can manually view the "Provisioned Services" link.)
Figure out a way to get the provisioning results, possibly via a REST call after the redirect. (REST calls that trigger provisioning can just be documented to advise the caller to pull provisioning status manually.)
Attachments
Issue Links
- is related to
-
CO-2454 Notifications on Job Failures
- Open
-
CO-913 Notification on Provisioner Failure
- Resolved
-
CO-1310 Make JobShell Fully Asynchronous
- Resolved
-
CO-1419 Review Handling of Provisioning on Database Save Failure
- Open
-
CO-77 Batch outbound/Reporting
- Open
-
CO-854 Provisioner Status Report
- Open
-
CO-863 posixAccount Support
- Resolved