review the publication

[jburel]

This PR modifies the publication workflow. It uses the command line directly since I have not found an action allowing us to specify the name since it was previously not ignored if declared in meta/main.yml. See https://github.com/ansible/galaxy/pull/2767/files

The role name is extracted from the meta/main.yml and specified as a command line argument.
If this approach works, changes should be added to https://github.com/ome/action-ansible-galaxy-publish (repository is currently read-only)

[sbesson]

See also https://forum.ansible.com/t/ansible-galaxy-s-role-import-enhancements-and-fixes-for-the-new-year/3206/2 which describes a very similar issue.

The proposed change i.e. passing the role name via an option at the command-line is consistent which the workaround described by the Galaxy developers in https://forum.ansible.com/t/ansible-galaxy-s-role-import-enhancements-and-fixes-for-the-new-year/3206/3.

Reading the upstream code a bit, an possible alternative approach would be to rename this repository to avoid starting with ansible-role as this would prevent the auto-computed alternate_role_name from overriding role_name in the metadata. Is it worth following-up on the forum to ask for clarifications on the official behavior?

[jburel]

That is also an option.
I think we need to come to a general consensus.
The renaming of the repo avoid having to maintain an action since the current GHA will work

[jburel]

using --role-name seems to be the most suitable approach cf. reply on forum post

[jburel]

Change made to ome/action-ansible-galaxy-publish#1