-
Notifications
You must be signed in to change notification settings - Fork 659
porting guide 2.19 - describe lazy complex var eval impact on builtin filters/tests #2639
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
base: devel
Are you sure you want to change the base?
Conversation
… for common Jinja2 filters/tests
@s-hertel sorry for the delay here - do you agree with the suggested edits or are there still open questions on this PR? |
Would be great to get this merged before the ansible-core 2.19.0 release happens. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@s-hertel I didn't mean my review to cause too much delay. Shall we merge and make any improvements or detailed explanations as follow ons?
Sorry for not following up sooner. I wanted to see how ansible/ansible#85201 would play out (whether my advice would help them, and if there were any better workarounds or whether more related changes would trickle in for 2.19). Feel free to merge this, and I'll follow up if I can improve it in the future. |
Also feel free to push changes directly to my branch, @oraNod if you want to clarify anything, like your suggested change. This didn't get stuck because of your review, just my uncertainty if it's complete or good enough. |
This is generally covered by https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_12.html#lazy-templating, but t I think it would be helpful to give a couple examples as well.