Deprecate `role_name` in `meta/main.yml`
See original GitHub issueDuring the Galaxy CLI Developer Workflow meeting we decided that Galaxy and Mazer should no longer synthesize the role (or repository) name, and therefore role_name
needs to be deprecated.
For reference see: https://docs.google.com/document/d/1nx65quXCyYORNel72rRCovyQo_qO5fhHlqrnKyYNlYU/edit?usp=sharing
To let users know about this change, we need to start issuing a deprecation warning in the import output whenever role_name
is found in meta/main.yml
.
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
What is the correct syntax of defining role dependencies in the ...
Updating the meta/main.yml according this snippet as follows: dependencies: - src: 030.firewall version: 0.1.0 name: 030.firewall - src: ...
Read more >Creating Roles — Ansible Documentation
To override the default name, set the role_name attribute in the role meta/main.yml file. The following snippet from a meta/main.yml file ...
Read more >role meta/main.yml dependency with source control repository ...
Using ansible 2.1.0.0. I'd like to have a role that lists private source control repositories like this in the meta/main.yml: dependencies:
Read more >Unable to override role name with meta/main.yml role_name ...
You are mixing up two things: the repository name in which the role is versioned remotely and the directory name in which the...
Read more >Replace all references to the old role name - OpenDev
Replace all references to the old role name ... tripleo_ansible/roles/tripleo_firewall/molecule/firewall-remove-complex/playbook.yml.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
A datapoint for your consideration:
As users of Galaxy our setup is broken by this proposal. The repos that back our Galaxy roles are in some cases widely used, forked and cloned. They all use the implicit naming convention of an
ansible-role-
prefix.We have just been hit by having all our roles unexpectedly renamed to use underscores. What do you suggest users like us (and users of our roles) should do to maintain consistent developer and user experiences?
Deprecating
role_name
is a terrible idea considering the fact that this is what people started doing to give their role the name they actually wanted rather thanansible_role_blah_blah
… given than the regex to remove theansible_role
part was removed quite recently… this is going to be another costly blow and major annoyance to many users who have just reconfigured their pipelines.Also, why did you remove the hyphens? Only noticed this change today and this seems like another, quite frankly, poorly justified change that adds little benefit.