generated from ansible-collections/collection_template
-
Notifications
You must be signed in to change notification settings - Fork 80
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
ansible.utils filters should raise AnsibleFilterError #209
Comments
Urth
added a commit
to Urth/ansible.utils
that referenced
this issue
Sep 29, 2022
Qalthos
pushed a commit
to Urth/ansible.utils
that referenced
this issue
Oct 14, 2022
Qalthos
pushed a commit
that referenced
this issue
Oct 14, 2022
This was referenced Nov 3, 2022
Closed
Closed
ghost
mentioned this issue
Nov 5, 2022
1 task
This was referenced Nov 5, 2022
This was referenced Nov 5, 2022
Merged
This was referenced Nov 16, 2022
Closed
Closed
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
With the changes from PR149 ansible.utils raises the base
AnsibleError
for invalid input values instead ofAnsibleFilterError
. Where possible the more specific error should be raised.An example of this can be seen with ansible-lint where the
AnsibleError
triggers thejinja[invalid]
linting rule. If the filters would useAnsibleFilterError
it would see that the problem lies with a filter, not with the template itself.ISSUE TYPE
COMPONENT NAME
ansible.utils filters
ANSIBLE VERSION
COLLECTION VERSION
OS / ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: