foodogsquared/ansible-playbooks
1
0
Fork 0
mirror of https://github.com/foo-dogsquared/ansible-playbooks.git synced 2025-01-31 10:58:15 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
20 Commits 1 Branch 0 Tags 67 KiB
916296c6d8
Commit Graph

4 Commits

Author SHA1 Message Date
Gabriel Arazas
de8af8b8f0 system/base: update and migrate to Ansible 5 2022-06-13 08:58:23 +08:00
Gabriel Arazas
90afaf9503 Improve system/base role 2022-03-19 12:32:27 +08: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
Gabriel Arazas
7581863a4f Modularize tasks into roles 
Now, it's becoming similar to my NixOS configuration. Not as declarative
and working out of the box as it requires a server but it's the closest
thing. I'll explore more configurations as I go along.
 2022-03-17 17:38:47 +08:00