New ansibug release

I’ve been a bit slack in keeping it up to date with new Ansible versions but in celebration of Ansible 2.22 I’ve just pushed a new ansibug release as well as an update to the VSCode extension:

As well as fixing support Ansible 2.21+, that introduced some internal changes around register projections, I’ve also tried to focus a bit more on the user experience and this release includes some nice things like:

  • Better logic for finding a valid Python environment as well as better logging and errors around this
  • Playbook codelens action to debug or debug with arguments from the editor rather than requiring a launch configuration
  • Task redo support to rerun a failured task rather than having to restart the whole playbook
  • Better completion support in the debug console

You can see more information about what this extension can do as well as some of the examples and what it looks like in VSCode at Home - ansibug.

If you have any ideas or suggestions on how this could be made better I would love to hear it.

2 Likes

Just thinking out loud here.
I think it would be a good feature to have ansibug and ara-ansible combined. Meaning when you run playbook in debug mode all the execution is saved to local sqlite db so user can review them later / compare them (in ara like ui).

I am personally (and my agent) debug with local instance of ara. Combining both approaches (ara and DAP) can give some interesting results.

Did you try to use ansibug with an agent? Can you share your experience? Do agents understand DAP protocol?