Cloud computing infrastructure pipelines with run triggers

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.

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.