OVERVIEW:

1. Ad-hoc commands (simple linux) ← No idempotency
2. Modules → Single work
3. Playbooks (More than one module)

Ad-hoc Commands in Ansible:

Purposes of Ad-hoc Commands in Ansible:

1. Immediate Execution:
   • Ad-hoc commands allow you to execute tasks immediately on remote hosts. This is useful for urgent changes or when you need to run a task without delay.
2. Testing and Troubleshooting:
   • They are excellent for testing and troubleshooting. You can test individual modules and commands to see how they perform on remote hosts before including them in a more comprehensive playbook.
3. Simple, One-off Tasks:
   • Ideal for simple, one-off tasks that do not require the complexity of a full playbook. Examples include restarting a service, checking disk usage, or applying a quick configuration change.
4. Quick Changes and Maintenance:
   • Useful for performing quick changes and maintenance tasks on servers, such as updating packages, changing configurations, or managing users.
5. Learning and Experimentation:
   • New users can experiment with different modules and commands to learn how Ansible works. Ad-hoc commands provide an interactive way to understand module usage and syntax.
6. Consistency and Automation:
   • Even though they are for single tasks, ad-hoc commands still leverage Ansible’s inventory and configuration management, ensuring consistency and repeatability across different environments.

Benefits of Ad-hoc Commands:

1. Efficiency:
   • Save time by avoiding the need to create, edit, and run a playbook for simple tasks.
2. Flexibility:
   • Allow you to target specific hosts or groups dynamically, providing flexibility in managing your infrastructure.
3. Simplicity:
   • Simplify the execution of straightforward tasks, reducing the complexity associated with playbooks for minor operations.