Priyam Sahoo

We have a PR ready with debugging options for playbook execution. #1006

Duplicate of #1042. PR is welcome.

Hey @gionn, we are working on a better way of discovering interpreters. But till then, here's a quick tip: Rather than changing all these settings, you can use `ansible.python.activationScript` and...

The fix to this is to add appropriate paths in the settings as mentioned by @AppeninTerenceBARBE above. If using virtual environments, you can simply add this setting, and it should...

@iamgini, it is hard for us to reproduce the scenario. Is it possible for you to provide more info on the setup, or maybe if you could create a branch...

@dmorawetz, this might not be the correct solution as it is breaking a lot of end-to-end tests with our supported VS Code Ansible extension. Please look into it.

@jamesholland-uk, we are working on this issue, and it will soon be fixed. Thanks for using the extension and raising the bug!

@max06, it seems like your vscode is not open in the correct / desired environment. Try selecting the appropriate python interpreter from the settings.

This will surely be fixed in the coming updates of the extension.

@Gaibhne, Ansible Support is the option that shows the output. You have 2 options under it: `message`, which gives generic messages, and `verbose`, which gives more detailed outputs. Furthermore, I...