I'm not connecting the dots somehow but there's a dependency behavior that I can't seem to create. It's slightly different from the current definition of optional_all. Currently, optional_all dependency is satisfied when the dependency is running, disabled, or in maintenance. Specifically, an optional_all dependency is not satisfied when it's in offline waiting for its dependencies.
Basic, I'd like to have A "optionally" depends on B to behave as: - if B is not enabled, A can still come online - if B is enabled, it MUST be running for A to come online. The rationale here is a particular core functionality of A is activated only when B is enabled. If B is in maintenance, service A should also be offline or in maintenance since the its activated functionality cannot operate properly. Is such behavior available? If not, does it make sense to have such behavior (file RFE)? Thanks, tony
