Is it a best practice to use Ansible-Galaxy roles in playbooks instead ansible-modules in playbooks? [closed]
Clash Royale CLAN TAG #URR8PPP 1 I have an Ansible playbook for establishing LAMP environments on remote machines. Part of this playbook deals with installing Composer: - name: Install Composer get_url: url: https://getcomposer.org/installer dest: /tmp/composer-setup.php command: php /tmp/composer-setup.php --install-dir=/usr/local/bin --filename=composer My consideration Instead these 5-lines structure I was thinking of using this ansible-galaxy command inside the playbook: ansible-galaxy install geerlingguy.composer geerlingguy.composer is the most communally supported AG role with more than million users (so I assume that if there is a problem and Jeff isn't around at the moment - say, took vacation in Hawaii or something, there will be many community members to fix the problem and ensure stability. Using this will also shorten my already quite-long playbook. My question In general, is it a best practice to use Ansible-Galaxy roles with tasks and tests in an ...