Ad hoc commands
On most occasions, there is a call to use an actual playbook, but when things start getting to playbooks within playbooks, or maybe information is needed on another host that is not in the inventory, it’s possible to get creative. We have never actually found a reason to use the ad hoc modules and roles; however, it is good to know that they are there. Additionally, if there ever was a reason to use them, it would be in a CI/CD job outside of the Automation controller.
The modules have several important inputs as follows:
module_name: The name of the module to use. This is limited, but more modules can be added in the Automation controller settings.module_args: The arguments to use for the command.inventory: Inventory to use for the command.credential: Credential to use for the command.interval: The interval to use when checking for an update on the job.timeout: Time to wait on the job to end.wait: Boolean, whether to...
