On Fri, 20 Oct 2023 08:40:56 -0700 (PDT)
Veera wrote:
> the "cols" are printed as like below (not as [green, red, yellow,
> blue]).
> ...
> "msg": [
> [
> "green",
> "toronto",
> "English"
> ],
> [
> "red",
>
Hi Vladimir,
Thanks . It helps to learn a lot.
Any recommended link to learn the jinja2 formatting?.
in btw, the "cols" are printed as like below (not as [green, red, yellow,
blue]).
is there ansible/jinja version conflict or I miss a bit?
- name: playbook to print the list as table
Hi Vladimir,
Thanks . It helps to learn a lot.
Any useful like to learn jijna2 in details will be helpful .
in Btw, why the "cols" are printed as like below , instead of you have
mentioned? is there ansible/jinja version conflict or I miss a bit?
- name: playbook to print the list as table
short answer:
Because collections
long answer:
Since we added the 'collections' feature we also introduced
namespaces, including for the modules that existed before collections
(version 2.9), they CAN still use the 'short name' or 'module name' as
you called it, even for modules that were
Hi Vladimir,
I am really interested in learning how you provide such code.
>From where can I learn more?
Warm regards,
Abhi
On Fri, 20 Oct 2023, 16:08 Vladimir Botka wrote:
> Declare the list of columns
>
> fnames: [color, cities, lang]
>
> and get the columns
>
> cols: |
> {% filter
Declare the list of columns
fnames: [color, cities, lang]
and get the columns
cols: |
{% filter from_yaml %}
{% for i in fnames %}
- {{ lookup('vars', i ) }}
{% endfor %}
{% endfilter %}
gives
cols:
- [green, red, yellow, blue]
- [toronto, montreal, mumbai,
Hi,
Looking for a template which prints the list's items in the horizontal
(rows) of a tables.
I have the below list and trying to print as a table.
vars:
color:
- green
- red
- yellow
- blue
cities:
- toronto
- montreal
- mumbai
- dubai
In FCQN , "builtin" exists for only ansible's builtin(native) modules .
We have other modules too from community or vendors ..
https://docs.ansible.com/ansible/latest/collections/index_module.html
On Friday, October 20, 2023 at 4:53:19 PM UTC+5:30 Rowe, Walter P. (Fed)
wrote:
> It is now
It is now recommended that all modules be called by their FQCN (fully qualified
community name).
These ansible.builtin.file and file are the same, but ansible.builtin.file will
always guarantee which file module you mean to reference in case some other
community package also has a module named
Hello Team,
I just want to know why we have builtin for all modules in ansible earlier
it was just module name
--
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
10 matches
Mail list logo