Ability for customer to specify an application patch’s default action
For provided patch content, please provide the ability for customers to set (change) the Default action to one other than the provided default.
Patch Policy can only enact a patch’s default action. However, many patches have non-default actions which are preferable. These are often for user-facing applications (Chrome, Firefox, Office apps, etc). For these, Action 2 first kills the running process, then installs the patch.
This change would allow customers to use Patch Policy for actions where supplemental actions are preferable.
Do you think all user-facing applications should be handled the same way?
I.e. if I defined a certain class of client should “KillAppsToPatch”, could I define that globally, or would I need one setting for Chrome and another for Java and a third for Office, etc.?
I think of all of these the same way – that the app is user-facing. If there were a certain class of application (or class of application patches) with a property that can be harnessed, that would be useful.
Since this is motivated by Patch Policy, if it could be solved by a content property KillAppsToPatch and that property is inside the content, that’d probably be fine.