But basically, until we can save without needing a body/structure, during a "Deploy" we have to "run" transforms as part of the "save" path, rather than separately as part of an optional "run".
However, frontend needs to have the RunID ASAP in order to coordinate events.
For now, as soon as we know that a dataset is going to have to save & apply a transform as part of the Deploy, we need to generate a runID and pass it to the frontend through the ETAutomationDeployStart event.
layed out this in comment https://github.com/qri-io/frontend/issues/258#issuecomment-928196331
But basically, until we can save without needing a body/structure, during a "Deploy" we have to "run" transforms as part of the "save" path, rather than separately as part of an optional "run".
However, frontend needs to have the
RunIDASAP in order to coordinate events.For now, as soon as we know that a dataset is going to have to save & apply a transform as part of the
Deploy, we need to generate arunIDand pass it to the frontend through theETAutomationDeployStartevent.