We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
set_fact is a little dumb if you do:
set_fact: key={{ some_value | int }}
because that results in a string
but it's fine if you do:
set_fact: key: "{{ some_value | int }}"
or even
key: "{{ some_value }}"
It would be nice if the short form were a bit smarter, or maybe if the old form just raised a deprecation warning (preferred?)
The text was updated successfully, but these errors were encountered:
Dup of #5463
Sorry, something went wrong.
Remove set from junos_facts as it errors out (#5670)
f5658f4
Fix #5636 per @ganeshnalawade
No branches or pull requests
set_fact is a little dumb if you do:
set_fact: key={{ some_value | int }}
because that results in a string
but it's fine if you do:
set_fact:
key: "{{ some_value | int }}"
or even
key: "{{ some_value }}"
It would be nice if the short form were a bit smarter, or maybe if the old form just raised a deprecation warning (preferred?)
The text was updated successfully, but these errors were encountered: