Timeline for Should the Tag #ansible-playbook be merged into the Tag #ansible?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 28, 2019 at 6:37 | comment | added | womble Mod | Sorry, I'm not feeling like you're making your case. If "ansible" is a recognisable separate thing from "ansible-playbook", then perhaps both tags should stay, but with improved descriptions as to when each is applicable? | |
| Dec 28, 2019 at 5:43 | comment | added | 0xSheepdog | (continued). Using the tags this way is like having separate tags for python commands directly versus writing python code into a file and executing that script. Do we need separate tags in that scenario? If not, why do we do it for Ansible? | |
| Dec 28, 2019 at 5:42 | comment | added | 0xSheepdog | So "Ansible" is the name of the software but also the executable command and the most basic form of the tool. That basic tool is used in "Ad Hoc" mode which works great, but really isn't useful for large sweeping operations in the way Ansible is usually discussed and considered. Technically, that command is "ansible-playbook", and requires the user provide a .YAML formatted file, the 'playbook'. Ansible-tower is the enterprise automation framework and GUI that runs ansible-playbook, and Galaxy is the "docker hub" of ansible roles/plays that others have written and shared. | |
| Dec 28, 2019 at 3:14 | history | answered | wombleMod | CC BY-SA 4.0 |