Alex, +1
I think these changes, combined with the recent docker sensor/effector changes from Iulana Cosmina, massively reduce the need to drop out of yaml into Java. This is a win a) by reducing the barrier to entry for the average sys admin who is used to just getting things done without the need to compile code and b) by capturing the logic of a blueprint more clearly in the blueprint itself. I've seen Apache Brooklyn users attempt to implement some of these features within their local organisation a few times. So it really makes sense that we make it a core, fully developed, feature. I think replayability and retryability are really nice additions as well. thanks Duncan On Wed, 24 Aug 2022 at 18:57, Geoff Macartney <geom...@apache.org> wrote: > Hi Alex, > > This looks very interesting - I've just glanced through it so far but will > try to read it in detail soon. I'll certainly be very interested to hear > what everyone thinks. > > Cheers > Geoff > > > > On Wed, 24 Aug 2022 at 16:44, Alex Heneveld <a...@cloudsoft.io> wrote: > > > Hi folks, > > > > I'd like Apache Brooklyn to allow more sophisticated workflow to be > written > > in YAML. > > > > As many of you know, we have a powerful task framework in java, but only > a > > very limited subset is currently exposed via YAML. I think we could > > generalize this without a mammoth effort, and get a very nice way for > users > > to write complex effectors, sensor feeds, etc, directly in YAML. > > > > At [1] please find details of the proposal. > > > > This includes the ability to branch and retry on error. It can also give > > us the ability to retry/resume on an Apache Brooklyn server failover. > > > > Comments welcome! > > > > Best > > Alex > > > > > > [1] > > > > > https://docs.google.com/document/d/1u02Bi6sS8Fkf1s7UzRRMnvLhA477bqcyxGa0nJesqkI/edit?usp=sharing > > >
