I have an update that returns exit code 0 even when we require a reboot for a SSO component.
Problem: Citrix Workspace LTSR sso does not work until I reboot after installation.
Workaround: Deploy and upgrade using customized Application User Experience to require reboot prompt
Ideal Solution: Extend Scriptrunner and the Publisher to allow configurable Reboot (soft) , Reboot (hard) on updates when success is received.
I dont envision users to remap reboot needed to no reboot, but custom exit code mapping like ConfigMgr would be nice to see as well for update that are really just an application and scriptrunner.