Community survey: Help us identify tooling used in Ansible collection developers and maintainers community

[Andersson007]

Hello Community!

We, the Ansible community engineering team, would like to better understand
all the tooling currently in use by our community of collection developers
and maintainers for building, testing, releasing, publishing,
and distributing Ansible collections.
This will help us see if there’s something to optimize or to focus on more.

Please check all tools you use from the two lists below.
If something is not present in the list, please put all the missed tools
in a comment with a sentence what it’s used for.
You feedback is much appreciated!

Part 1

• ansible-galaxy (CLI tool)
• ansible-creator
• collection_template repo
• community collection bot
• antsibull-docs
• antsibull-changelog
• ansible-test
• molecule
• ansible-lint
• GitHub Actions
• Azure Pipelines
• Zuul (publishes coll-s artifacts on Galaxy based on tags)
• ansible-builder
• ansible-navigator
• other collections containing dependencies for other collections
• ansible-sign
• pytest-ansible
• tox-ansible
• ansible-dev-environment
• vscode ansible extension

Part 2

• ansible-dev-tools (if you install some of the above tools with this package, choose it too)
• galaxy-importer
• ansible-content-actions
• github-action-build-collection
• github-action-test-galaxy-import
• ansible-test-gh-action
• other (add a comment)

Thanks for your feedback!

[russoz]

I also use andebox by yours truly. andebox · PyPI

It is a WIP, but I use it on a regular basis to: run tests (sanity, unit, integration) in docker and integration tests in vagrant VMs, generate docsites locally, and the latest addition, reformatting YAML docs inside python code.