ASYNCHRONOUS MECHANISM FOR PROCESSING SYNCHRONOUS OPERATION FLOWS

1 . A method, comprising:

receiving a request from an orchestrator engine to determine a state of a cloud resource of a cloud automation platform;

propagating the request to the cloud automation platform;

caching a task identifier received from the cloud automation platform responsive to the request;

receiving data indicative of the state of the cloud resource from the cloud automation platform wherein the data is associated with the task identifier; and

providing the data to the orchestrator engine.

2 . The method of claim 1 , wherein the orchestrator engine is configured to communicate synchronously and wherein the cloud automation platform is configured to communicate asynchronously.

3 . The method of claim 1 , wherein the method includes receiving the data indicative of the state of the cloud resource responsive to a completion of an operation by the cloud automation platform.

4 . The method of claim 1 , wherein the method includes broadcasting an event to each of a plurality of instances of a service.

5 . The method of claim 4 , wherein the method includes processing the event by one of the plurality of instances to associate the data with the task identifier.

6 . The method of claim 5 , wherein the method includes ignoring the event by others of the plurality of instances.

7 . The method of claim 1 , wherein the cloud automation platform is Idem.

8 . A non-transitory machine-readable medium having instructions stored thereon which, when executed by a processing resource, cause the processing resource to:

receive a request from an orchestrator engine to determine a state of a cloud resource of a cloud automation platform;

propagate the request to the cloud automation platform;

cache a task identifier received from the cloud automation platform responsive to the request;

receive data indicative of the state of the cloud resource from the cloud automation platform wherein the data is associated with the task identifier; and

provide the data to the orchestrator engine.

9 . The medium of claim 8 , wherein the orchestrator engine is configured to communicate synchronously and wherein the cloud automation platform is configured to communicate asynchronously.

10 . The medium of claim 8 , including instructions to receive the data indicative of the state of the cloud resource responsive to a completion of an operation by the cloud automation platform.

11 . The medium of claim 8 , including instructions to broadcast an event to each of a plurality of instances of a service.

12 . The medium of claim 11 , including instructions to process the event by one of the plurality of instances to associate the data with the task identifier.

13 . The method of claim 12 , including instructions to ignore the event by others of the plurality of instances.

14 . The medium of claim 8 , wherein the cloud automation platform is Idem.

15 . A system, comprising:

a request engine configured to receive a request from an orchestrator engine to determine a state of a cloud resource of a cloud automation platform;

a propagate engine configured to propagate the request to the cloud automation platform;

a cache engine configured to cache a task identifier received from the cloud automation platform responsive to the request;

a state engine configured to receive data indicative of the state of the cloud resource from the cloud automation platform wherein the data is associated with the task identifier; and

a provision engine configured to provide the data to the orchestrator engine.

16 . The system of claim 15 , wherein the orchestrator engine is configured to communicate synchronously and wherein the cloud automation platform is configured to communicate asynchronously.

17 . The system of claim 15 , wherein the state engine is configured to receive the data indicative of the state of the cloud resource responsive to a completion of an operation by the cloud automation platform.

18 . The system of claim 15 , wherein the propagate engine is configured to broadcast an event to each of a plurality of instances of a service.

19 . The system of claim 18 , wherein the state engine is configured to process the event by one of the plurality of instances to associate the data with the task identifier.

20 . The system of claim 19 , wherein the state engine is configured to ignore the event by others of the plurality of instances.