3

No, you cannot nest jinja2 expansion i.e. the following won't work: # Warning ! Those will fail ! some_var: "{{ some_dict[{{ some_dynamic_key }}] }}" other_var: "{{ {{ dynamicaly_prefixed }}_var }}" # Did I forget to say the above examples will fail ? But you can use your var without any problem, just as in almost any other programming ...


2

Ansible facts are data collected about the (target) systems on which Ansible takes actions. They are variables, but set by Ansible (in a way like system defined variables). They are collected during Gathering Facts stage of a playbook run, and it is controlled by the gather_facts setting. Ansible calls this variables discovered from systems. That said, it is ...


1

I believe you should be able to reference the namespace name like so: namespace_name = azurerm_eventhub_namespace.eventhub[0].name However, if the namespace_name field is a required parameter on the resources you are passing it to, you might run into other issues while you are trying to set enabled to false, as the resources depend on the output of the ...


1

Not to contradict anything written in @Ceshadri_C's answer, but to focus more on the difference between facts and variables - perhaps the variable precedence page could be of greater insight. The difference between facts and variables set is defined by their precedence, i.e. all variables are important, but some variables are more important than others. In ...


Only top voted, non community-wiki answers of a minimum length are eligible