Dependency-aware rules engine for delivering managed package upgrades

A non-transitory machine-readable storage medium that provides instructions that, if executed by a processor, are configurable to cause said processor to perform operations comprising:

• receiving, over a network, a package dependency graph from a first operating entity via a first API call that expresses relationships between a set of managed software packages;
• ingesting a subscriber set subscribed to the set of managed software packages via a second API call to a second operating entity that owns the managed software packages;
• constructing a per-subscriber dependency graph expressing relationships between the individual subscriber's delivery operations;
• executing delivery of the set of managed software packages based on dependency order of the per-subscriber dependency graph, while applying rules including one or more of:
• push schedule rules that allow the first operating entity to specify time-based gates before which delivery is not to be attempted;
• and
• subscriber exclusion rules that allow the first operating entity to exclude specific subscribers and those subscribers who have old software product versions.

An apparatus comprising:

• a processor;
• a non-transitory machine-readable storage medium that provides instructions that, if executed by the processor, are configurable to cause the apparatus to perform operations comprising,
• receiving, over a network, a package dependency graph from a first operating entity via a first API call that expresses relationships between a set of managed software packages;
• ingesting a subscriber set subscribed to the set of managed software packages via a second API call to a second operating entity that owns the managed software packages;
• constructing a per-subscriber dependency graph expressing relationships between the individual subscriber's delivery operations;
• executing delivery of the set of managed software packages based on dependency order of the per-subscriber dependency graph, while applying rules including one or more of:
• push schedule rules that allow the first operating entity to specify time-based gates before which delivery is not to be attempted;
• and
• subscriber exclusion rules that allow the first operating entity to exclude specific subscribers and those subscribers who have old software product versions.