Feature request · API & developer experience · Blocks work
Run flows on remote infrastructure without creating a deployment for each
1 source thread · first seen 2025-02
Summary
Multi-infrastructure workflows force a separate deployment per flow plus run_deployment, causing deployment sprawl and brittle coupling to server-side names. The author wants direct submission to remote infrastructure.
- Affects
- teams running workflows across several infrastructures
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“they are forced to create a deployment for each workflow and use run_deployment to invoke the created deployment”