New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change default of TRANSFORM_INVALID_GROUP_CHARS from 'never' to 'ignore' #70908
Comments
Files identified in the description: If these files are incorrect, please update the |
!component =lib/ansible/inventory/group.py |
I support this change. |
Files identified in the description: If these files are incorrect, please update the |
Files identified in the description: If these files are incorrect, please update the |
This horse has been beat to something that no longer looks like a horse. We've discussed this again in our triage meeting, and we believe that the current configuration addresses both sides of this concern. However neither side is necessarily 100% happy with the outcome. I believe we have concluded the zero-sum game here. We warn to let users know they may have issues with invalid chars, but we don't implicitly modify those entries any longer. |
closing as per above. |
SUMMARY
After the long and drawn out issue ansible/ansible-documentation#89 was mostly concluded by un-deprecating dashes in group names, I noticed that my Ansible installations are still spitting out warnings by default when using inventory plugins that build group names based on things like AWS regions.
I propose that the default for
TRANSFORM_INVALID_GROUP_CHARS
be changed from'never'
to'ignore'
.It's also unclear to me what value there is in having a
'never'
option, since it just does nothing of substance... and then spits out a warning? It seems like a scary message indicating something could break if I ignore it, but nothing does break, so I wonder what's the point of displaying the message?ISSUE TYPE
COMPONENT NAME
lib/ansible/inventory/group.py
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
macOS 10.15.5.
STEPS TO REPRODUCE
inventory.ini
contents:main.yml
contents:Run the playbook with:
EXPECTED RESULTS
No warnings appear.
ACTUAL RESULTS
When I run with
-vvvv
it says:But I'm not sure how that's actionable or why it matters enough to throw a warning.
The text was updated successfully, but these errors were encountered: