collection uses and expects "execution_environment.yml" as opposed to ansible-builder default "execution-environment.yml"

[David-Igou]

Currently the build step in this collection expects the file execution_environment.yml (uses and underscore, instead of a dash) which is not the default ansible-builder expects, nor is it configurable. This creates compatibility issues for users attempting to leverage this collection coming from default usage of ansible-builder, giving an inconsistent experience.

This only effects users that already have a rendered execution-environment.yml ready when invoking the role, as opposed to generating it.

Issue Type

• Bug Report

I feel that this slightly leans towards this being more of a bug report than feature request.

Desired Behavior

ideally, the file name should be a parameter, but it's probably best it defaults to the pattern presented to most users learning the tool

STEPS TO REPRODUCE

Any user that follows the ansible-builder build docs will follow a pattern that makes their code incompatible with the collection

[djdanielsson]

yea I noticed this a while ago, and we had talked about changing the file name. I agree we probably should make the change to be the same as the default file name builder looks for