# Jinja2 warning using conditionnals **URL:** \ **Category:** Get Help\ **Tags:** ansible, jinja2\ **Created:** [March 5, 2024, 11:18am UTC](https://forum.ansible.com/t/jinja2-warning-using-conditionnals/4218 "2024-03-05T11:18:31Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![motorbass](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@motorbass](https://forum.ansible.com/u/motorbass)\ **Post date:** [March 5, 2024, 11:18am UTC](https://forum.ansible.com/t/jinja2-warning-using-conditionnals/4218/1 "2024-03-05T11:18:31Z")
Hi I’m using the following tasks to add servers to my AD Domain only if there’s not already joined. ```auto - name: Domain discovery ansible.builtin.shell: | realm discover my_domain.net register: join - name: Domain joining ansible.builtin.expect: command: realm join my_domain.net -U {{ domain_account }} --install=/ responses: Password for *: "{{ domain_password }}" when: join.stdout_lines is search('configured{{":"}} no') ``` - 1st task is used to keep command line result into a register - 2nd task is used to add server to the domain only if I found “configured: no” in the previous result I record in the register. This is what is very important to me- to detect if server have to be add or not. - Note: I must to escape the semicolon with {{ " "}} else the task fails cause it’s seen as a YAML syntax. Here’s the content of the register I’m using. ```auto ok: [X.X.X.X] => { "join": { "changed": true, "cmd": "realm discover my_domain.net\n", "delta": "0:00:00.036477", "end": "2024-03-05 12:02:17.484044", "failed": false, "msg": "", "rc": 0, "start": "2024-03-05 12:02:17.447567", "stderr": "", "stderr_lines": [], "stdout": "my_domain.net\n type: kerberos\n realm-name: my_domain.net\n domain-name: my_domain.net\n configured: no\n server-software: active-directory\n client-software: sssd\n required-package: sssd-tools\n required-package: sssd\n required-package: libnss-sss\n required-package: libpam-sss\n required-package: adcli\n required-package: samba-common-bin", "stdout_lines": [ "my_domain.net", " type: kerberos", " realm-name: my_domain.net", " domain-name: my_domain.net", " configured: no", " server-software: active-directory", " client-software: sssd", " required-package: sssd-tools", " required-package: sssd", " required-package: libnss-sss", " required-package: libpam-sss", " required-package: adcli", " required-package: samba-common-bin" ] } } ``` As you can see, stdout\_lines is a list of list, BUT, there is a 2 spaces in front of every line after quotes. Example `" configured: no"` instead of `"configured: no"` **Problem :** Both tasks are working well, but I still got a warning on the second one `[WARNING]: conditional statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: join.stdout_lines is search('configured{{":"}} no')` - I’ve tested to select list, but in the case of configured is set to yes, there’s more lines and so, list selection isn’t fair. - I can’t use `selectattr` as this isn’t YAML format. - I know i can use `regex_search` in case of debug (like `"{{ join.stdout_lines | regex_search('configured: no') }}"` but I can’t use it with the `when` conditionnal. I’m looking for a solution or a best practices of filtering data to avoid this warning. Thanks for your reading, Gael ---
**Author:** ![shertel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/shertel/32/1241_2.png) [@shertel](https://forum.ansible.com/u/shertel)\ **Post date:** [March 5, 2024, 12:10pm UTC](https://forum.ansible.com/t/jinja2-warning-using-conditionnals/4218/2 "2024-03-05T12:10:17Z")
> [@motorbass](#): > > I know i can use `regex_search` in case of debug (like `"{{ join.stdout_lines | regex_search('configured: no') }}"` but I can’t use it with the `when` conditionnal. Did you try wrapping the whole thing in `"`? `when: "join.stdout_lines | regex_search('configured: no')"` Conditionals are already templated (string or list of strings), so the brackets shouldn’t be included in the expression. ---
**Author:** ![motorbass](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@motorbass](https://forum.ansible.com/u/motorbass)\ **Post date:** [March 5, 2024, 12:21pm UTC](https://forum.ansible.com/t/jinja2-warning-using-conditionnals/4218/3 "2024-03-05T12:21:31Z")
Just tested it and it works ! So it means when using ` " "` in a conditional, all the content is seen as ‘ansible content’ and not interpreted like yaml/json etc… ? Another thing learn today 🙂 thanks a lot @shertel ---
**Author:** ![shertel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/shertel/32/1241_2.png) [@shertel](https://forum.ansible.com/u/shertel)\ **Post date:** [March 5, 2024, 12:28pm UTC](https://forum.ansible.com/t/jinja2-warning-using-conditionnals/4218/4 "2024-03-05T12:28:36Z")
It’s just a way to escape `:` and ensure it’s a string (not a dictionary). You could also use a [folded block scalar](https://yaml-multiline.info/): ```auto when: >- join.stdout_lines | regex_search('configured: no') ``` ---
**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\ **Post date:** [March 5, 2024, 6:38pm UTC](https://forum.ansible.com/t/jinja2-warning-using-conditionnals/4218/5 "2024-03-05T18:38:11Z")
I know you already have a solution, but I thought you might enjoy this snippet. This converts all values to string (since login-formats: for e.g. may have an invalid leading character ‘%’), and converts each discovered domain as a yaml dictionary. ```yaml - name: Domain discovery ansible.builtin.shell: >- realm discover my_domain.net | sed 's/:\s\(.*\)/: "\1"/g;s/\([[:alnum:]]$\)/\1:/g' register: join - name: Domain joining ansible.builtin.expect: command: realm join my_domain.net -U {{ domain_account }} --install=/ responses: Password for *: "{{ domain_password }}" when: (join.stdout | from_yaml)['my_domain.net']['configured'] == "no" ``` Also, it’s important to note that you can join a realm or domain using different casing than the default discovery casing, and each casing will show up as different realms. For e.g. `realm discover` may show you configured as a member of My\_Domain.net, but not my\_domain.net, even though they may be the exact same realm-name/domain-name in the results. This behavior will create false positives if you’re not careful, in your/@shertel’s example or mine. In my example though, you can be case specific on the realm you’re acting upon, and is particularly useful in case you are working with multiple realms. Additionally, if you’re joining to ActiveDirectory, you might find `adcli info my_domain.net` and `adcli testjoin` useful as well. `adcli info my_domain.net` is less ambiguous about casing, and `adcli testjoin` will validate that the host is a trusted member of its domain, not just configured to one (although it doesn’t let you specify a realm, it does let you specify a keytab, which you should have multiple of in multi-realm scenerios). ---
**Author:** ![motorbass](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@motorbass](https://forum.ansible.com/u/motorbass)\ **Post date:** [March 7, 2024, 7:26am UTC](https://forum.ansible.com/t/jinja2-warning-using-conditionnals/4218/6 "2024-03-07T07:26:52Z")
@Denney-tech thanks for your solution too, it’s a bit more complex but as you said it may works better in case of different casing scenarios. Thanks also for the advice on `adcli ` I have to try this for sure ! ---
**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\ **Post date:** [April 6, 2024, 7:27am UTC](https://forum.ansible.com/t/jinja2-warning-using-conditionnals/4218/7 "2024-04-06T07:27:16Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.