There is a lot of useful general info here on YAQL. In the Orquesta pages the approach seems to have been to just point to the YAQL and Jinja projects themselves?

Are we happy to remove the pages and just refer to the YAQL/Jinja projects or want to put a page together for Orquesta/YAQL and Orquesta/Jinja?

I would vote for a page for Orquesta/YAQL and Orquesta/Jinja. But this shouldn't be a blocker for this PR imho.

This is the example used in the unit-tests, but I couldn't get notify in Orquesta working in my setup - but I may be missing something. In the Orquesta pages we just mention there is a notify parameter that we can ignore for now...

I got Orquesta notifications working but I also had to add on a notify section as well as the notify parameters, e.g. I also had:

notify:
  on-complete:
    routes:
      - slack
    message: "Succeeded"

so that it had the details of route etc.

Do we think the documentation as is is ok, or

1. should I add in the notify section into the example
2. Should I add in a preceding sentence along following lines:

The method for specify the route and conditions for when tasks in an Orquesta workflow is the same as ActionChain. You have a notify section in the action meta when registering.

and should I put in a notify section

@LindsayHill @armab Having got notifications working in Orquesta now, I'm wondering if more needs to go into this
section on the chatops page. Or alternatively I was mis-understanding something.

@LindsayHill @armab Having got notifications working in Orquesta now, I'm wondering if more needs to go into this
section on the chatops page. Or alternatively I was mis-understanding something.

So as not to confuse things, I will merge this PR. And generate a new PR with enhancements that I think will make Orquesta notifications even clearer.

👍 step by step