78568ab207
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. |
||
|---|---|---|
| files/dconf | ||
| inventory | ||
| playbooks | ||
| roles | ||
| ansible.cfg | ||
| README.adoc | ||
Resources
This configuration may evolve into an abominable framework of configuration over time. At some point, it won’t be the simple "Hello World"-esque reference for Ansible. If you’re looking where to start learning about this, I’ve saved a list of them from the beginning:
-
Fedora Magazine’s article with a very simple example. This is where I first found about it and the very beginning of the Ansible usage journey.
-
Some already existing configurations laying out and about on the internet…
-
Justin W. Flory’s Ansible playbooks are a nice example on getting a complete configuration with Ansible.
-
fabaff’s Ansible playbook for Fedora is a perfect example for Fedora-specific configurations and it is simpler compared to the previously mentioned examples.
-
89luca89’s Ansible playbook for a minimal Fedora installation. It’s a simpler example than the previous making it easier to explore the features.
-