RH294 Ch 1: Ansible Configuration and ansible-navigator

Name: WebAsha Technologies
Address: Pune, Maharashtra, IN

The nodes are already reachable as `devops` with SSH keys and `~/ansible/inventory` exists (node1 in `dev`, node2 in `test`). Configure Ansible and ansible-navigator for the project, run your first ad-hoc commands and learn to look things up in the execution environment.

Tasks

Create ~/ansible/ansible.cfg: inventory ./inventory, remote user devops, privilege escalation enabled with sudo to root, no password prompt.
Create ~/ansible/ansible-navigator.yml that uses the execution environment utility.lab.example.com/ee-supported-rhel10:latest, never pulls the image, and uses stdout mode.
With an ad-hoc command, make /etc/motd on all nodes contain exactly the line Managed by Ansible.
With an ad-hoc command, create the user automation on all nodes.
Use ansible-navigator doc and ansible-navigator collections to look things up, and write to ~/ansible/findings.txt: the fully qualified name of the module that manages firewalld rules, and the version of the community.general collection inside the execution environment (two lines).