ansible-playbooks/main.yml at 4af9c46e37a31fd127f0f5c6ba52ee7b27f9e9a5 - ansible-playbooks - foodogsquared's code forge

foodogsquared/ansible-playbooks

mirror of https://github.com/foo-dogsquared/ansible-playbooks.git synced 2025-01-31 04:58:10 +00:00

Gabriel Arazas 78568ab207 Modularize tasks from system/base to its own role

Seems like I misunderstood what tags are for. They're not individual
flags for the play, they're commonly used for excluding/including tasks
at runtime (e.g., `ansible-playbook $PLAYBOOK --tags $TAGS`). When
running a playbook, it will execute all tasks by default.

Think of them as attaching a label and letting the user choose from the
playbook run. Setting multiple tags at the playbook-level seems to be
the best practice as seen from jwflory's Ansible playbooks.

2022-03-19 12:32:19 +08:00

12 lines

266 B

YAML

Raw Blame History

 ---
 - name: Install fonts
   dnf:
     state: present
     name:
       - adobe-source-code-pro-fonts
       - adobe-source-sans-pro-fonts
       - adobe-source-serif-pro-fonts
       - google-noto-emoji-fonts
       - google-noto-sans-fonts
       - google-noto-serif-fonts