Chapter 27. Using the sudo system role

Procedure

1. Create a playbook file, for example ~/playbook.yml, with the following content:

   ---
   - name: "Configure sudo"
     hosts: managed-node-01.example.com
     tasks:
       - name: "Apply custom /etc/sudoers configuration"
         ansible.builtin.include_role:
           name: redhat.rhel_system_roles.sudo
         vars:
           sudo_sudoers_files:
             - path: "/etc/sudoers"
               user_specifications:
                 - users:
                     - <user_name>
                   hosts:
                     - <host_name>
                   commands:
                     - <path_to_command_binary>

   The settings specified in the playbook include the following:

   users

   The list of users that the rule applies to.

   hosts

   The list of hosts that the rule applies to. You can use ALL for all hosts.

   commands

   The list of commands that the rule applies to. You can use ALL for all commands.

   For details about all variables used in the playbook, see the /usr/share/ansible/roles/rhel-system-roles.sudo/README.md file on the control node.

2. Validate the playbook syntax:

   $ ansible-playbook --syntax-check ~/playbook.yml

   Note that this command only validates the syntax and does not protect against a wrong but valid configuration.

3. Run the playbook:

   $ ansible-playbook ~/playbook.yml

Verification

1. On the managed node, verify that the playbook applied the new rules.

   # cat /etc/sudoers | tail -n1
   <user_name> <host_name>= <path_to_command_binary>