Files
openstack-ansible-rabbitmq_…/tasks/rabbitmq_feature_flags.yml
Dmitriy Rabotyagov 858b79056d Auto-fix usage of modules via FQCN
Since ansible-core 2.10 it is recommended to use modules via FQCN
In order to align with recommendation, we perform migration
by applying suggestions made by `ansible-lint --fix=fqcn`

Change-Id: Id8a34727251ade1a1b2d5a881e5ee5e808b495dc
2025-02-13 08:44:28 +01:00

30 lines
1.2 KiB
YAML

---
# Copyright 2024, BBC
#
# 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: "Check for disabled RabbitMQ feature flags"
ansible.builtin.command: "rabbitmqctl list_feature_flags --formatter json name state stability"
register: _feature_flags
changed_when: false
failed_when: false
# NOTE: changed_when required despite the above check because 'unstable'
# feature flags will remain disabled each time this runs
- name: "Enable missing RabbitMQ feature flags"
ansible.builtin.command: "rabbitmqctl enable_feature_flag {{ flag['name'] }}"
changed_when: false
loop: "{{ _feature_flags.stdout | from_json | rejectattr('stability', 'eq', 'experimental') | selectattr('state', 'eq', 'disabled') }}"
loop_control:
loop_var: flag