ansible-ops-management/role-rocky-rabbitmq.yml

---
# Stands up a RabbitMQ Cluster
- name: Configure RabbitMQ
  hosts: all
  become: true
  vars_files:
    # vars/vaults/encpass.yml
    - vars/common.yml
    - vars/rabbitmq.yml

  # This is to try to avoid the handler issue in pre/post tasks
  handlers:
    - import_tasks: handlers/main.yml

  pre_tasks:
    - name: Check if ansible cannot be run here
      stat:
        path: /etc/no-ansible
      register: no_ansible

    - name: Verify if we can run ansible
      ansible.builtin.assert:
        that:
          - "not no_ansible.stat.exists"
        success_msg: "We are able to run on this node"
        fail_msg: "/etc/no-ansible exists - skipping run on this node"

    # We have separate passwords per rabbitmq env
    - name: Import rabbitmq passwords
      ansible.builtin.include_vars:
        file: "vars/vaults/rabbitmq_{{ rabbitmq_env }}.yml"

    # The extras repos has epel-release provided
    - name: Enable the EPEL repository
      ansible.builtin.dnf:
        name: epel-release
        state: present
      notify:
        - enable_crb
      tags:
        - packages

    - name: Flush handlers
      ansible.builtin.meta: flush_handlers

    # This will change eventually to a rocky-release-messaging repo or to a
    # rocky-release-rabbitmq repo
    #- name: Install centos rabbitmq
    #  yum:
    #    name: centos-release-rabbitmq-38
    #    state: present
    #  tags:
    #    - packages

  roles:
    - role: rockylinux.ipagetcert
      state: present
      when: rabbitmq_private

    - role: rockylinux.rabbitmq
      state: present

  post_tasks:
    - name: Touching run file that ansible has ran here
      ansible.builtin.file:
        path: /var/log/ansible.run
        state: touch
        mode: '0644'
        owner: root
        group: root
...