Baseline currently executes all configured steps as root (as it generally should), which of course enables it to install packages, run scripts to use the jamf binary, etc.
In the case of something like setting a dock configuration with a script, it'd be neat to have a per-script key for Baseline to run that item as the currently signed-in user to avoid the script author or user having to handle this logic.
I realize the use case for this is fairly specific, though I'm sure there are other scenarios I can't think of at the moment. Totally understand if this is too niche to bother implementing!
Baseline currently executes all configured steps as root (as it generally should), which of course enables it to install packages, run scripts to use the jamf binary, etc.
In the case of something like setting a dock configuration with a script, it'd be neat to have a per-script key for Baseline to run that item as the currently signed-in user to avoid the script author or user having to handle this logic.
I realize the use case for this is fairly specific, though I'm sure there are other scenarios I can't think of at the moment. Totally understand if this is too niche to bother implementing!