New Service State: Operator Intervention

[reset]

We currently have an up and down service state. Services are either running or they are not and they are expected to eventually be consistent. This can lead to a bad user experience when starting a service for the first time. Perhaps you missed applying a configuration field? You'll need to go check the logs to see that the service is outputting an error. What's worse is a service automatically updates and is immediately broken because you may have forgotten to apply it's new configuration before the update was received and applied.

These issues can be resolved by adding an intervene state which requires an operator to perform a specific action to get the service up and running. There are three features been requested which we could build once this new state is added:

• Services have been "seeded" with updates and you want to require an operator to issue a command to signal to the service group that they may proceed with their update.
• A service is started but it is missing a required configuration field. This is best represented by something which cannot have a sensible default or is sensitive data, like a database password.
• A service is updated and a new configuration field which is required is present in the update.

[stale[bot]]

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[bot]]

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[bot]]

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.