Add new hooks for more complete service lifecycle control

[christophermaier]

In order to run effectively, services may need more control over their lifecycle than Habitat currently provides.

By using new hooks that run at additional control points, we can provide users with Habitat packages that are better tuned to the specific needs of their services.

Some concrete examples are provided in the linked issues, but further research and community engagement should be done to determine the final suite of hooks to add.

[themightychris]

I was just asking about something like this in Slack. Are you talking about defining a bunch upfront or letting users add their own arbitrary service hooks?

I'm picturing something like hab pkg exec but instead hab svc exec that takes a service identifier and runs a rendered hook of your own with proper environment

The trick though is how do you prevent user hook names from conflicting with future habitat hooks and keep people from Frankensteining with the standard hooks? They'd go really nicely just sitting in the hooks folder along the others but the core team can't be worried about adding new hooks blowing custom stuff up

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale]

This issue has been automatically closed after being stale for 400 days. We still value your input and contribution. Please re-open the issue if desired and leave a comment with details.