Comment 3 for bug 1877448

> Two thoughts there. One would be that you could have a configuration hook that you'd want to run on install for "zero configuration". Basically to init things.

I feel that I must mention that the configure hook already runs at install time as well as configure time, but that doesn't really invalidate your point. Particularly because I really wish it didn't do that.

> The other would be that you have an interface hook that would be on multiple interfaces.

Typically those hooks are actually doing things specific to the interface though. That feels pretty hand-wavy.

I want to re-state that I'm on board with the generally idea presented here. However, I wonder if the added complexity of the triggers is worth it given that, if we assume the original proposal for a moment, you could easily have the same executable triggered on multiple events with the following:

hooks:
  configure:
    command: my-executable
  pre-refresh:
    command: my-executable

This also supports the more complex use-case you mention, where if someone needed to run a complex set of steps upon a given event, they could just write an executable for it and specify it there.