Felix Fontein wrote: >Hi,
>that change was apparently caused by >https://github.com/ansible/ansible/pull/69278 >I have no idea why it was made, though. I have done further digging on this and come up with the following: The template in question is actually used as part of a dictionary: ``` # Define the resource tags # If not updated by the CI system, put a placeholder deploy tag which indicates local deployment # ANSIBLE_CALLER_USERNAME environment variable is set using the Docker wrapper script deploy_version: "locally deployed by {{ lookup('env', 'ANSIBLE_CALLER_USERNAME') }}" resource_tags: Platform: "{{ platform_name }}" Stage: "{{ environment_type }}" DeployTag: "{{ deploy_version }}" ``` If I print this out in a debug statement then the tags dictionary is correct and also resources are deployed using the correct tags data. The part that is failing is an assertion: ``` - name: Validate variables that need to be defined by calling role assert: that: "{{ item }} is defined" msg: "Variable {{ item }} is not defined" quiet: yes with_items: "{{ required_vars | default ([]) }} " ``` In this example resource_tags is in a list of required_vars we want defining and its giving us the error at the point it tries to assert the variable exists. Thanks. Andrew. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/DB8PR08MB50336E18A16379C13758A2EFAFF90%40DB8PR08MB5033.eurprd08.prod.outlook.com.
