Cloud computing infrastructure pipelines with run triggers

1. A computer-implemented method comprising:

identifying a run trigger between a first node and a second node, the first node maintaining configuration for a first portion of a cloud computing infrastructure associated with executing a first portion of a cloud-based application on the cloud computing infrastructure, the second node maintaining configuration for a second portion of the cloud computing infrastructure associated with executing a second portion of the cloud-based application on the cloud computing infrastructure, the run trigger initiating in response to an action at the first node and comprising a source identifier and a destination identifier, wherein the source identifier is an identifier of the first node and the destination identifier is an identifier of the second node;

planning a first run on the first node, the first run including a first process executed on the first portion of the cloud computing infrastructure with data at least temporarily stored on the first node and associated with the source identifier, wherein the first run comprises the action;

queuing a second run on the second node based on the run trigger, the second run including a second process executed on the second portion of the cloud computing infrastructure with data received and at least temporarily stored by the second node and associated with the source identifier; and

executing the first run on the first node, wherein the first run causes the cloud computing infrastructure to modify one or more infrastructure resources associated with the first portion of the cloud computing infrastructure, the first run generating a state file that is an input to the second run, the state file listing the one or more infrastructure resources in use after the first run.

2. The method of claim 1 , further comprising:

planning the second run on the second node; and

executing the second run on the second node, wherein the second run causes the cloud computing infrastructure to modify one or more infrastructure resources associated with the second portion of the cloud computing infrastructure.

3. The method of claim 2 , wherein executing the second run on the second node further comprises:

identifying one or more additional runs on the second node, each of the one or more additional runs being associated with an additional run source identifier;

comparing the run source identifier of the run to the additional run source identifiers; and

aborting the run if the run source identifier matches at least one of the additional run source identifiers.

4. The method of claim 1 , wherein the first node is a workspace, and the process is a second process.

5. The method of claim 1 , wherein the first node is a module, and wherein the method further comprises:

before identifying the run trigger, modifying the first node in a module registry, the module registry comprising a database of a plurality of modules, wherein the modification comprises the action.

6. The method of claim 1 , wherein before identifying the run trigger, the method further comprises:

creating the run trigger between the first node and the second node.

7. The method of claim 6 , wherein creating the run trigger further comprises:

determining that the run trigger does not form a loop.

8. The method of claim 7 , wherein determining that the run trigger does not form a loop comprises:

identifying one or more descendants of the second node, wherein each descendant of the one or more descendants is a node connected by a subsequent run trigger to the second node or a descendant of the second node; and

determining that the identifiers of the one or more descendants of the second node do not include the identifier of the first node.

9. The method of claim 1 , wherein identifying the run trigger comprises:

querying a run trigger database with the source identifier; and

receiving the destination identifier from the run trigger database.

10. The method of claim 1 , wherein the second node is a workspace.

11. A system comprising:

at least one data processor; and

at least one memory storing instructions which, when executed by the at least one data processor, result in operations comprising:

identifying a run trigger between a first node and a second node, the first node maintaining configuration for a first portion of a cloud computing infrastructure associated with executing a first portion of a cloud-based application on the cloud computing infrastructure, the second node maintaining configuration for a second portion of the cloud computing infrastructure associated with executing a second portion of the cloud-based application on the cloud computing infrastructure, the run trigger initiating in response to an action at the first node and comprising a source identifier and a destination identifier, wherein the source identifier is an identifier of the first node and the destination identifier is an identifier of the second node;

planning a first run on the first node, the first run including a first process executed on the first portion of the cloud computing infrastructure with data at least temporarily stored on the first node and associated with the source identifier, wherein the first run comprises the action;

queuing a second run on the second node based on the run trigger, the second run including a second process executed on the second portion of the cloud computing infrastructure with data received and at least temporarily stored by the second node and associated with the source identifier; and

executing the first run on the first node, wherein the first run causes the cloud computing infrastructure to modify one or more infrastructure resources associated with the first portion of the cloud computing infrastructure, the first run generating a state file that is an input to the second run, the state file listing the one or more infrastructure resources in use after the first run.

12. The system of claim 11 , wherein the operations further comprise:

planning the second run on the second node; and

executing the second run on the second node, wherein the second run causes the cloud computing infrastructure to modify one or more infrastructure resources associated with the second portion of the cloud computing infrastructure.

13. The system of claim 11 , wherein the first node is a module, and wherein the operations further comprise:

before identifying the run trigger, modifying the first node in a module registry, the module registry comprising a database of a plurality of modules, wherein the modification comprises the action.

14. The system of claim 11 , wherein before identifying the run trigger, the operations further comprise:

creating the run trigger between the first node and the second node.

15. The system of claim 14 , wherein creating the run trigger further comprises:

determining that the run trigger does not form a loop.

16. The system of claim 15 , wherein determining that the run trigger does not form a loop comprises:

identifying one or more descendants of the second node, wherein each descendant of the one or more descendants is a node connected by a subsequent run trigger to the second node or a descendant of the second node; and

determining that the identifiers of the one or more descendants of the second node do not include the identifier of the first node.

17. The system of claim 11 , wherein executing the run on the second node further comprises:

identifying one or more additional runs on the second node, each of the one or more additional runs associated with an additional run source identifier;

comparing the run source identifier of the run to the additional run source identifiers; and

aborting the run if the run source identifier matches at least one of the additional run source identifiers.

18. The system of claim 11 , wherein identifying the run trigger comprises:

querying a run trigger database with the source identifier; and

receiving the destination identifier from the run trigger database.

19. The system of claim 11 , wherein the second node is a workspace.

20. A non-transitory computer-readable storage medium storing instructions, which when executed by at least one data processor, result in operations comprising:

identifying a run trigger between a first node and a second node, the first node maintaining configuration for a first portion of a cloud computing infrastructure associated with executing a first portion of a cloud-based application on the cloud computing infrastructure, the second node maintaining configuration for a second portion of the cloud computing infrastructure associated with executing a second portion of the cloud-based application on the cloud computing infrastructure, the run trigger initiating in response to an action at the first node and comprising a source identifier and a destination identifier, wherein the source identifier is an identifier of the first node and the destination identifier is an identifier of the second node;

planning a first run on the first node, the first run including a first process executed on the first portion of the cloud computing infrastructure with data at least temporarily stored on the first node and associated with the source identifier, wherein the first run comprises the action;

queuing a second run on the second node based on the run trigger, the second run including a second process executed on the second portion of the cloud computing infrastructure with data received and at least temporarily stored by the second node and associated with the source identifier; and

executing the first run on the first node, wherein the first run causes the cloud computing infrastructure to modify one or more infrastructure resources associated with the first portion of the cloud computing infrastructure, the first run generating a state file that is an input to the second run, the state file listing the one or more infrastructure resources in use after the first run.