Enforcement of dependencies

Current Situation

• Dependencies are enforced when objects are changed:
  • If an object is renamed, for example a job resource, then the referencing workflow is updated and is put to draft mode. Deplloyment of both objects is enforced.
  • The same proceding applies in case that objects are modified but are not renamed.
• While it is useful for a number of situations to have all dependent objects deployed, there can be situations when objects are modified but not renamed and users wish to deploy individual objects without enforcement of dependencies.

Desired Behavior

• The /inventory/deployables API provides the information if a draft object enforces dependencies as it was renamed or if a draft object can be deployed without enforcing dependencies.
• The GUI
  • enforces dependencies if renamed objects are deployed (unchanged behavior).
  • gives users a choice (from a checkbox) to deploy objects based on dependencies if objects are modified but not renamed. By default dependencies are active for deployment.