Conversation
|
Thanks for opening @rockaut! Do you think the current Ansible definition could be suitable or adapted for your scenario? https://github.com/microsoft/vscode-dev-containers/tree/main/containers/azure-ansible |
|
Sorry I missed the comments. I will have a look at it again over the day. |
@bamurtaugh IDK ... I guess it could. But should it be? If you pack all the Ansible tools into, it would bloat the azure side of things and also the other way around I guess. Then there is also the question for the usability/understandability for the users. I guess a lot of people would wonder about the "azure" part of the devenv? |
|
Thanks for your response @rockaut. I think this definition would be a great fit for community hosting and publishing. We recently announced the process for creating and distributing Features, and we're discussing a similar process for templates / definitions here - please let us know if you have any thoughts or questions! |
|
Sounds good to me, thx. |
A simple devcontainer (based on the python-3) for developing Ansible projects and collections/roles - without ballast not really needed.