mirror of
https://github.com/foo-dogsquared/ansible-playbooks.git
synced 2025-01-31 04:58:10 +00:00
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.
23 lines
374 B
YAML
23 lines
374 B
YAML
---
|
|
- name: Install i18n tools
|
|
dnf:
|
|
state: present
|
|
name:
|
|
- fcitx5
|
|
- fcitx5-configtool
|
|
- fcitx5-gtk4
|
|
- fcitx5-lua
|
|
- fcitx5-mozc
|
|
- fcitx5-rime
|
|
- librime
|
|
- librime-tools
|
|
- mozc
|
|
|
|
- name: Install fonts for i18n
|
|
dnf:
|
|
state: present
|
|
name:
|
|
- google-noto-cjk-fonts
|
|
- google-noto-cjk-fonts-common
|
|
|