Add ability to change apt/yum package state
The current method of installing the distribution packages required is set in the tasks and cannot be changed by a deployer. Currently the apt task always installs the latest package. This results in unexpected binary changes when a deployer may simply be trying to execute a configuration change. This patch adds the ability for a deployer to change the desired state so that the results are predictable. Change-Id: I3227dc6f15e0307926e65427bc635c34e2baa87f
This commit is contained in:
4 changed files with 19 additions and 2 deletions
@@ -16,6 +16,10 @@
## APT Cache Options
cache_timeout:600
# Set the package install state for distribution packages
# Options are 'present' and 'latest'
rabbitmq_package_state:"latest"
# Inventory group containing the hosts for the cluster
rabbitmq_host_group:"rabbitmq_all"
13
releasenotes/notes/package-state-bb93a1d4b272425d.yaml
Normal file
13
releasenotes/notes/package-state-bb93a1d4b272425d.yaml
Normal file
@@ -0,0 +1,13 @@
---
features:
- The rabbitmq_server role now supports the ability to configure whether
apt/yum tasks install the latest available package, or just ensure
that the package is present. The default action is to ensure that
the latest package is present. The action taken may be changed to
only ensure that the package is present by setting
``rabbitmq_package_state`` to ``present``.
upgrade:
- The rabbitmq_server role always checks whether the latest package is
installed when executed. If a deployer wishes to change the check to
only validate the presence of the package, the option
``rabbitmq_package_state`` should be set to ``present``.
@@ -33,7 +33,7 @@
- name:Install RabbitMQ package dependencies
apt:
pkg:"{{ item }}"
state:latest
state:"{{ rabbitmq_package_state }}"
register:install_packages
until:install_packages|success
retries:5
@@ -24,7 +24,7 @@
- name:Install RabbitMQ package dependencies
yum:
pkg:"{{ item }}"
state:latest
state:"{{ rabbitmq_package_state }}"
update_cache:yes
register:install_packages
until:install_packages|success
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.