Hey, thanks for flagging this, both Magnus and Ronnie.
Agreed. The Automations API request list / start / follow-up automation agents is big enough to keep in a separate thread from config-as-code. That keeps the signal clean for each topic. I reopened 166898, so we can continue the API discussion there:
@Ronnie_Kilsbo, your setup a graph of about 20 automations and monitoring executions via your own CLI is exactly the kind of thing that’s worth writing up there in detail. What are the absolute blockers for you, and what’s nice to have. That’s the best way to boost the signal.
We’ll keep discussing config-as-code here and in related threads:
I can’t share a specific timeline yet, but there’s interest in this direction. If we have an update, we’ll post it in the threads.