[vinayan3]

To me it looks like a REPL for Ansible. If it does let you build each task in a cell then you could develop the whole playbook interactively and incrementally. It could reduce the turn around time of having to run a long playbook and waiting till the latest step you wrote.

[throwaway5752]

Doesn't ansible core have ansible console already? This seems very bizarre and solution in search of a problem. An alexa skill for ansible would be interesting, but I wouldn't use it, either.

edit: https://docs.ansible.com/ansible/latest/cli/ansible-console.... "REPL console for executing Ansible tasks."

[kbumsik]

What Jupyter (regardless of its kernel: Ansible, Python etc...) does is just adding a GUI interface on top of an existing REPL console you mentioned. For example, you already have a working iPython REPL console, you don't really need the heavy Jupyter system to run scientific Python codes.

If you prefer to use the REPL consoles directly for your own propose then Jupyter will add no value on it. However, Jupyter let you save results for each commands without running them again, and you can add Markdown documentations. This is useful when you want document your codes (with results) and share them with others.

Jupyter is merely a productivity tool like an IDE, not a framework. Jupyter may not be suitable for running production codes anyway.

[flossyspeaker]

That makes sense, but you could also just tag that step and run it with the tag if you are testing it.