Why not allow for both variants? Add commands[].args. If it is present, treat commands[].command as single binary and call it with the args in commands[].args and if commands[].args is absent, interpret commands[].command as shell script. Same for hooks[].

If that gets too complex, I would prefer keeping the .args variant and adding it to commands[], as this is more readable for commands / hooks with more than a few parameters.

@mgruener That sounds like a smart way of allowing both. Should be straight forward to implement: if len(args) == 0 { run command in shell } else { run command using args (no shell interpretation) }

@FabianKramm What do you think?

Yes sounds good to me

As a variant of what @LukasGentele suggests, it could be done using docker's convention: if command is a list, then interpret as binary w/ arguments; if it is a string, then treat it as something to be run in a shell.