Dmitriy Rabotyagov 78fbffd20c Move RabbitMQ restart to handlers
Due to historical reasons RabbitMQ operations, like start/stop/restart
were perfromed in tasks and triggered on changes.

As of today there seems to be no need in such approach and we can use
handlers instead.

It will also move some tasks, which intend to run when service is
running, to their own file. This also allows to run them once on cluster
rather then for each host.

We also merge set_cookie with post_install as there is no reason to
maintain the task in it's own file.

Change-Id: I222b9de3ca531724b05c7fa2cf032a3271055d64
2024-11-05 15:05:16 +00:00

41 lines
1.1 KiB
YAML

---
# Copyright 2024, Cleura AB
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
- name: "Ensure RabbitMQ is stopped"
service:
name: rabbitmq-server
state: stopped
listen:
- RabbitMQ stop
- RabbitMQ restart
- name: "Ensure RabbitMQ is started"
service:
name: rabbitmq-server
state: started
enabled: yes
listen:
- RabbitMQ start
- RabbitMQ restart
- name: Wait for rabbitmq to be started
wait_for:
host: "{{ item.key }}"
port: "{{ item.value }}"
loop: "{{ query('dict', rabbitmq_port_bindings.tcp_listeners) }}"
listen:
- RabbitMQ start
- RabbitMQ restart