-
Notifications
You must be signed in to change notification settings - Fork 55
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
filter_names does not document or gracefully handle spaces #362
Comments
If someone does look at resolving this issue can they please make sure that they retain support for %20 being used instead of a space. Now that the current workaround/limitation/design feature is known I like others will be coding scripts using %20 and it will be a problem if a future update goes and breaks the scripts. |
By the way, my initial work around was fine for spaces but wouldn't handle other special characters that might cause issues with a url. I've switched to using the urlencode filter to be more comprehensive.
|
The modules are autogenerated by: https://github.com/ansible-collections/vmware_rest_code_generator version: 2.2.1 Closes: ansible-collections#362
protect the URL parameters See: ansible-collections/vmware.vmware_rest#362
The modules are autogenerated by: https://github.com/ansible-collections/vmware_rest_code_generator version: f4bbe71330eab0684aee08ab3d2baf4463f93774 Closes: ansible-collections#362
bump auto-generated modules The modules are autogenerated by: https://github.com/ansible-collections/vmware_rest_code_generator version: f4bbe71330eab0684aee08ab3d2baf4463f93774 Closes: #362
As the person who first raised this, thanks to everyone for firstly a workaround and then secondly a final fix. |
Just as a follow-up as I've just started to update systems. The old matching of %20 to a space has not been retained after a fix was put in place to allow the correct matching of spaces. The result is a change to the historic way in which this works. |
SUMMARY
The _info modules provide a method of filtering names but will fail on names that contain a space. If the module does not gracefully handle names with spaces it should at least be documented how names should be written to be tolerated by the modules. Adding a '%20' in place of a space seems to make the module function as expected.
ISSUE TYPE
COMPONENT NAME
vmware.vmware_rest.vcenter_datacenter_info
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
If the user leaves any values without spaces using a _info module it will fail to filter. Quotes and backslashes will not work. Only adding the '%20' to the variables will result in the expected results.
The text was updated successfully, but these errors were encountered: