Conflict resolution for device-driven management
Disclosed are various embodiments for resolving conflicts between workflows in a workflow processing system. A plurality of workflows stored in a workflow queue are evaluated to identify a common dependency of the plurality of workflows. Then, a version hierarchy is created for the common dependency of the plurality of workflows, the version hierarchy identifying multiple versions of the common dependency. In response to execution of a first one of the plurality of workflows stored in the workflow queue, the version hierarchy can be evaluated to identify the most recent version of the common dependency. Then, installation of the most recent version of the common dependency can be initiated.
1. A system, comprising:
a computing device comprising a processor and a memory, and
machine-readable instructions stored in the memory that, when executed by the processor, cause the computing device to at least:
evaluate a plurality of workflows stored in a workflow queue to identify a common dependency of the plurality of workflows;
create a version hierarchy for the common dependency of the plurality of workflows, the version hierarchy identifying multiple versions of the common dependency;
in response to execution of a first one of the plurality of workflows stored in the workflow queue, evaluate the version hierarchy to identify a most recent version of the common dependency; and
initiate installation of the most recent version of the common dependency.
2. The system of claim 1 , wherein the machine-readable instructions stored in the memory, when executed by the processor, further cause the computing device to at least:
determine that the installation of the most recent version of the common dependency has failed;
in response to the determination that the installation of the most recent version of the common dependency has failed, evaluate the version hierarchy to identify a second most recent version of the common dependency;
initiate installation of the second most recent version of the common dependency; and
block execution of individual ones of the plurality of workflows that are dependent on the most recent version of the common dependency.
3. The system of claim 2 , wherein the machine-readable instructions stored in the memory, when executed by the processor, further cause the computing device to at least send a message to a management service that the individual ones of the plurality of workflows that are dependent on the most recent version of the common dependency have failed.
4. The system of claim 1 , wherein the machine-readable instructions stored in the memory, when executed by the processor, further cause the computing device to at least:
send a request to a management service for the plurality of workflows;
receive the plurality of workflows from the management service; and
store the plurality of workflows from the management service in the workflow queue.
5. The system of claim 1 , wherein the common dependency is a configuration file.
6. The system of claim 1 , wherein the common dependency is a library to be installed on the computing device.
7. The system of claim 1 , wherein the common dependency is an application to be installed on the computing device.
8. A computer-implemented method, comprising:
evaluating a plurality of workflows stored in a workflow queue to identify a common dependency of the plurality of workflows;
creating a version hierarchy for the common dependency of the plurality of workflows, the version hierarchy identifying multiple versions of the common dependency;
in response to execution of a first one of the plurality of workflows stored in the workflow queue, evaluating the version hierarchy to identify a most recent version of the common dependency; and
initiating installation of the most recent version of the common dependency.
9. The computer-implemented method of claim 8 , further comprising:
determining that the installation of the most recent version of the common dependency has failed;
in response to determining that the installation of the most recent version of the common dependency has failed, evaluating the version hierarchy to identify a second most recent version of the common dependency;
initiating installation of the second most recent version of the common dependency; and
blocking execution of individual ones of the plurality of workflows that are dependent on the most recent version of the common dependency.
10. The computer-implemented method of claim 8 , further comprising sending a message to a management service that the individual ones of the plurality of workflows that are dependent on the most recent version of the common dependency have failed.
11. The computer-implemented method of claim 8 , further comprising:
sending a request to a management service for the plurality of workflows;
receiving the plurality of workflows from the management service; and
storing the plurality of workflows from the management service in the workflow queue.
12. The computer-implemented method of claim 8 , wherein the common dependency is a configuration file.
13. The method of claim 8 , wherein the common dependency is a library file.
14. The method of claim 8 , wherein the common dependency is an application file.
15. A non-transitory, computer-readable medium comprising machine-readable instructions stored in a memory that, when executed by a processor of a client device, cause the client device to at least:
evaluate a plurality of workflows stored in a workflow queue to identify a common dependency of the plurality of workflows;
create a version hierarchy for the common dependency of the plurality of workflows, the version hierarchy identifying multiple versions of the common dependency;
in response to execution of a first one of the plurality of workflows stored in the workflow queue, evaluate the version hierarchy to identify a most recent version of the common dependency; and
initiate installation of the most recent version of the common dependency.
16. The non-transitory, computer-readable medium of claim 15 , wherein the machine-readable instructions stored in the memory, when executed by the processor, further cause the client device to at least:
determine that the installation of the most recent version of the common dependency has failed;
in response to the determination that the installation of the most recent version of the common dependency has failed, evaluate the version hierarchy to identify a second most recent version of the common dependency;
initiate installation of the second most recent version of the common dependency; and
block execution of individual ones of the plurality of workflows that are dependent on the most recent version of the common dependency.
17. The non-transitory, computer-readable medium of claim 16 , wherein the machine-readable instructions stored in the memory, when executed by the processor, further cause the client device to at least send a message to a management service that the individual ones of the plurality of workflows that are dependent on the most recent version of the common dependency have failed.
18. The non-transitory, computer-readable medium of claim 15 , wherein the machine-readable instructions stored in the memory, when executed by the processor, further cause the client device to at least:
send a request to a management service for the plurality of workflows;
receive the plurality of workflows from the management service; and
store the plurality of workflows from the management service in the workflow queue.
19. The non-transitory, computer-readable medium of claim 15 , wherein the common dependency is a library to be installed on the client device.
20. The non-transitory, computer-readable medium of claim 15 , wherein the common dependency is an application to be installed on the client device.