Writing one playbook in Jupyter is easy but creating a framework to enable their 100+ product teams to self-serve and create playbooks has been so intensive for them, they even started working on their internal SDK for it.
It was a lot of code and the lead felt like the Jupyter visual interface was harder to follow for instructions/runbooks.
With PlayBooks, we have tried to abstract out the entire execution engine and configuration to a intuitive user experience (our architecture is explained here -- https://slender-resolution-789.notion.site/PlayBooks-Documen... )
Your project seems nice! I'll give it a try ;-) Only thing, the Jupiter-like part is not clear enough.
1: https://docs.nurtch.com/en/latest/rubix-library/index.html
2: https://docs.gitlab.com/ee/user/project/clusters/runbooks/
The Jupyter part is reference to the cellular execution of tasks as per the preference of the users + being able to get execution / code next to each other. Both have been design principles for us from the get-go.
Just like how variables can be reused across cells in Jupyter, we plan to shortly introduce rules / conditionals creating interdependencies between variables in the PlayBooks steps.
Edit: Adding the a sample Playbook link here for reference -- https://sandbox.drdroid.io/playbooks/14