Group var not correctly cast to integer about ansible HOT 9 CLOSED

@sivel checked the module, it does not cast, so native is really your only avenue in this specific case.

from ansible.

Files identified in the description:

None

If these files are incorrect, please update the component name section of the description or use the component bot command.

from ansible.

This is expected without having jinja2 native enabled: https://docs.ansible.com/ansible/latest/reference_appendices/config.html#default-jinja2-native

The historical integration can only produce the following python data types:

• dict
• list
• set
• bool
• str

Any other data type emitted from a single templating operation can only result in a str. This is why you see that type_debug indicates the type as being an int but the result of the templating operation results in a str.

I should note that we do have a shortcut in the code, that if the variable referenced is singular, we can directly return it's real value, however using variables that refer to other variables prevents this functionality.

You have a few options.

1. Enable jinja2 native, may have other adverse affects
2. Follow the k8s module examples of reading the defintion using lookup('template', ...)
3. Don't use variables that refer to templates using other variables (just use ldap_port instead of openldap_port)

Note: When using lookup('template') you will not have to quote the jinja values, as that is working around a YAML "limitation", so it would just be: port: {{ openldap_port }}

from ansible.

or just add |int filter at consumption to cast it

from ansible.

@bcoca Not sure what you mean with "at consumption". You mean at the point I am passing the variable to the module using it's value? Because that doesn't work in my case:

- name: Create service
  k8s:
    state: present
    definition:
      kind: Service
      metadata:
        name: "openldapservice"
        namespace: "thenamespace"
      spec:
        ports:
          - name: "openldapport"
            protocol: TCP
            port: "{{ openldap_port | int }}" # doesn't work
            targetPort: "openldapport"

from ansible.

you should not even need to do that if port is defined as an integer, the module itself will cast it

from ansible.

Ok, but neither works (cast or not) when defining openldap_port as I did in the example I described (as reference to ldap_port, which is defined as integer). Are you suggesting that this should work, even with jinja2 native disabled?

from ansible.

yes, IF the port field is defined as an integer

from ansible.

Closing per above.

If you have further questions please stop by IRC or the mailing list:

• IRC: #ansible on irc.libera.chat
• mailing list: https://groups.google.com/forum/#!forum/ansible-project

See this page for a complete and up to date list of communication channels and their purposes:

• https://docs.ansible.com/ansible/latest/community/communication.html

from ansible.