How responsive should service-config-manager operations be?

[joseph-reynolds]

What are the expectations for how fast service-config-manager operations become effective? Does the API return before the operation completes, or does it wait for the change become effective? Can these be documented in the repo README?

For example, the operation to disable IPMI takes about 10 seconds to become effective. Specifically, after the API to disable IPMI returns, the IPMI service is still active for about 10 seconds, and then becomes disabled.

Is the usage pattern supposed to be:

1. Enable or disable the service and expect an immediate service change.
2. Enable or disable the service and then poll or listen to signals to find out when the service change is effective.
3. When enabling a service, it if has errors starting, how should that be communicated to the agent trying to start the service?