You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yeah, I admit this is a pain, a few years ago Ansible changed the convention for role names from kebab case to snake case (without providing any way to migrate to the new naming convention). I can't change the name in Galaxy now because it'll break anyone relying on the current name.
Ansible Galaxy is pushing everyone to move their roles into collections. When I get time to do that, I'll update to the new naming convention, as that'll be a breaking change anyway.
Hello @gantsign, after latest ansible-lint, now all playbooks that use ansible-role-visual-studio-code will fail until the name on Galaxy is
role_name: visual_studio_code
on meta/main.yml:ansible/ansible-lint#3566 (comment)
You can even put role_name as
visual-studio-code
it gets automatically converted as extensively documented here: https://galaxy.ansible.com/docs/contributing/creating_role.htmlWould you mind changing the name?
The text was updated successfully, but these errors were encountered: