22.9. Configuring Red Hat Lightspeed tags by using the rhc RHEL system role

Procedure

1. Store your sensitive variables in an encrypted file:

   1. Create the vault:

      $ ansible-vault create ~/vault.yml
      New Vault password: <password>
      Confirm New Vault password: <vault_password>

   2. After the ansible-vault create command opens an editor, enter the sensitive data in the <key>: <value> format:

      username: <username>
      password: <password>

   3. Save the changes, and close the editor. Ansible encrypts the data in the vault.

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

   ---
   - name: Managing systems with the rhc RHEL system role
     hosts: managed-node-01.example.com
     vars_files:
       - ~/vault.yml
     tasks:
       - name: Creating tags
         ansible.builtin.include_role:
           name: redhat.rhel_system_roles.rhc
         vars:
           rhc_auth:
             login:
               username: "{{ username }}"
               password: "{{ password }}"
           rhc_insights:
             tags:
               group: group-name-value
               location: location-name-value
               description:
                 - RHEL8
                 - SAP
               sample_key: value
             state: present

   The settings specified in the example playbook include the following:

   group: group-name-value

   Specifies the system group for organizing and managing registered hosts.

   location: location-name-value

   Defines the location associated with the registered system.

   description

   Provides a brief summary or identifier for the registered system.

   state: present|absent

   Indicates the current status of the registered system.

   注意

   The content inside the tags is a YAML structure representing the tags desired by the administrator for the configured systems. The example provided here is for illustrative purposes only and is not exhaustive. Administrators can customize the YAML structure to include any additional keys and values as needed.

3. Validate the playbook syntax:

   $ ansible-playbook --syntax-check --ask-vault-pass ~/playbook.yml

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

4. Run the playbook:

   $ ansible-playbook --ask-vault-pass ~/playbook.yml