community-topics VS vscode-ansible

There is a community vote on a new policy for community.general on which ansible-core versions will be supported in new major releases. Basically support for ansible-core versions will be dropped if they were EOL at least a few weeks before the major release. For the upcoming community.general 8.0.0, that means that it will drop support for ansible-core 2.11 and 2.12 and require at least ansible-core 2.13. Details can be found in the associated issue.

As mentioned in The Bullhorn #113, we've opened a community / steering committee vote on declaring ngine_io.exoscale an effectively unmaintained collection and remove it from the Ansible 10 community package. Since then, there has been a new release. As a result, the vote ended with the decision to keep the collection in the community package.

2023-07-12: Community WG meeting, 18:00 UTC (propose topics here)

Hi everyone. We're working on making Ansible community documentation a separate project to ansible/ansible. The purpose is to benefit the Ansible community by decoupling community doc initiatives from core release cycles. This change also removes the Ansible Core team as the gate for other doc related efforts that will meet community needs, such as putting source content for docs.ansible.com under the direct control of the Steering Committee. Overall this change is a first step towards providing greater access and ownership of docs.ansible.com to the Ansible community.

Looking for your feedback on making community docs a separate github project to ansible/ansible, starting with moving /docs from ansible/ansible to ansible/ansible-documentation. See this issue for details.

It looks like the netapp.elementsw collection is effectively unmaintained. According to the current community guidelines for collections, we consider removing it in a future version of the Ansible community package. Please see Unmaintained collection: netapp.elementsw for more information or to announce that you're interested in taking over the maintenance of (a fork of) netapp.elementsw.

The netapp.aws collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See the removal process for details on how this works.

As mentioned in The Bullhorn #98, we consider netapp.aws an effectively unmaintained collection. Therefore, we've opened a community / steering committee vote on removing it from the Ansible 10 community package.

2023-05-10: Community WG meeting, 18:00 UTC (propose topics here)

Work continues combining several pytest plugins for ansible.

The place to open issues for the plugin https://github.com/ansible/vscode-ansible

Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board

Ansible-VSCode extension 2.0.0 is out!

Si cela ne fonctionne toujours pas, soulève un problème Github ici https://github.com/ansible/vscode-ansible ou https://github.com/ansible/ansible-language-server avec des détails comme :

I asked the devtools team and here is their reply: "The telemetry data is sent to the Red Servers and are not publicly available. Though we have documented the usage data that we gather here."

Best place to read the changelog is at https://github.com/ansible/vscode-ansible/releases but marketplace only links to the embedded changelog file, which is not as good as the github releases page (hyperlinks,...)

Ansible extension for vscode/codium

Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board

For example one recent bug we found is that defining ANSIBLE_FORCE_COLOR=1 can prevent the extension from working. I do expect that a number of ansible users to configure that in env or in their ansible.cfg file,... Details https://github.com/ansible/vscode-ansible/issues/373 -- we plan to release a fix later this week for this one.

DevTools ↗