84ede176b9
In some cases, deployers may want to use a repo instead of a deb file (limited connectivity, repo mgmt tools already in place, ...) This commit introduces this behavior in an optional manner: The default behavior is still using a deb file. If using an external repository, the repo used will be RabbitMQ recommended one hosted on packagecloud.io. Change-Id: If366d7411cffd59e4988ceba6fc47eac2b384ddf
15 lines
573 B
YAML
15 lines
573 B
YAML
---
|
|
features:
|
|
- |
|
|
RabbitMQ Server can now be installed from different
|
|
methods: a deb file (default), from standard
|
|
repository package and from external repository.
|
|
Current behavior is unchanged. Please define
|
|
``rabbitmq_install_method: distro`` to use packages
|
|
provided by your distribution or
|
|
``rabbitmq_install_method: external_repo`` to use
|
|
packages stored in an external repo. In the case
|
|
``external_repo`` is used, the process will install
|
|
RabbitMQ from the packages hosted by packagecloud.io,
|
|
as recommended by RabbitMQ.
|