Ok nice gotcha thanks again for your input everyone 🙂 If all goes well @emre people following this workflow would NOT personally serialize and push flows to the locations, starting an agent would ‘do it for them’, and that is fundamentally the appeal. The idea even came out of the thought experiment of “how can we get someone to run something on cloud without ever opening a terminal” (this doesn’t really get us all the way there, but does take out the independent registration step at the terminal).
I think @Alex Cano hit the prospective use case on the head, this is more for an easy on-ramp that is more “clicky” to just get that first one up (maybe even off a repo of examples, before you even write any flow code yourself, so total newbies). We definitely think at some point people would need to/want to transition to the “I’ll handle this now” situation. Tbh we have been most concerned with getting in the way of people ready for or already doing the “I’ll handle this now” side of it if they try (or someone in their org tires) to mix and match registration workflows.
Definitely will take these thoughts back. Since this is more of an additional workflow than totally replacing something (like the environments idea) its probably a bit lower risk to go through with it but if we confuse people more it will have done the total opposite of what we wanted 😅