Gaps and Obstacles in Developing Collections with Ansible Builder

[Andersson007]

Summary

The context: we are now working on the Improve the Partner Certification Experience ANSTRAT-1330 .
To complete the Document the gaps and obstacles on collection workflow story, every community engineering team member independently went through a typical collection development workflow: created a collection with a module from scratch, configured GitHub including CI, published it on Galaxy, etc. trying to use Ansible development tools as much as possible and reflecting their experiences in the Obstacles and issues found with ADT Google doc along the way.

This issue summarizes the challenges and obstacles encountered by the Community Engineering team while developing collections using Ansible Builder. This feedback outlines key areas for improvement within the tool, focusing on actionable solutions to enhance user experience. We've also created an issue with general feedback on using ADT.

Documentation:

• Did 0.0.2 EE release. Struggled with podman holding onto the image created earlier so the EE wasn’t picking up v 0.0.2. With help, used --no-cache option for ansible-builder. This isn’t listed in the builder docs, but is in cli help.
• No info in the docs about a recommended location for an execution environment file? The community recommends having it under /meta.