merge upstream changes #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixing Yum repo
Update Python package name to python instead of python2, and use file install vs. package install by default Partially rolls back #654, though continues to allow the user to set the package via $rabbitmqadmin_package
Release 12.0.1
Update tests for rabbitmqctl version parsing
The rabbitmq_plugin resource use the "rabbitmq-plugins"-command when enumerating enabled plugins. Starting with rabbitmq 3.10, this command will output a informational message: 'Listing plugins with pattern ".*" ...' which can be hidden with the -s or -q parameter. However, this approach will break rabbitmq_plugin on older versions of RabbitMQ. This patch implements a workaround that simply ignores the outputted line if it exists. Fixes: #909
Make rabbitmq_plugin resource functional on RabbitMQ 3.10.x
Release 12.0.2
… that is alrady on master
Minor fix to resolve a linting check
Enable usage of custom list of plugins when using static config file
bump puppet/systemd to < 5.0.0
Release 12.1.0
When overriding local node name (using NODENAME environment variable), clustering does not work as tinit_node is tested again hostname or fqdn. By adding the optional local_node to specify which node is the current node we can fix this issue. Use case: a server with a public and a private interface, rabbitmq cluster nodes communicates through the private interface while hostname and fqdn resolves to the public interface (and that can't be changed because of other dependencies on the server). The only solution is to use dedictated name for the private interface.
cluster: add local_node settings
This fixes inconsistent logic to determine management ip address if the rabbitmq::management_ip_address parameter is not set, and makes sure all logic tries to look up the rabbitmq::node_ip_address parameter.
Fix detection of management_ip_address for rabbitmqadmin
Drop Puppet 6 support
modulesync 9.3.0
* Require package_apt_pin to be a non-empty string or number * Use `nil` instead of empty string in test for empty pin
- Add hosts entry for `foobar` in acceptance test step (resolves issue that was causing rabbitmq not to start) - Switch `rabbitmq::cluster[:local_node]` to have `catch_failures = true` vs `expect_failures = true`
Disallow empty string in `package_apt_pin`
…nt plugin (#1024) Add ssl options for client renegotiation to rabbitmq-server --------- Co-authored-by: kperronne <[email protected]>
Drop support for Debian 10, Ubuntu 18, and FreeBSD 12
Improve test coverage in main class spec
Improve test coverage
- Remove support for CentOS / RHEL 7 (breaking change) - Remove workarounds specific to EPEL and require_epel parameter (breaking change) - Add support for CentOS / RHEL 9 in metadata - Where repos_ensure is not set, install centos-release-rabbitmq-38 to support installing RabbitMQ from semi-official source - Add in some additional tests for coverage (followup to #1028) that were hard to test without a supported RedHat family OS in metadata Fixes #816 Signed-off-by: William Yardley <[email protected]>
Add support for CentOS / RHEL 9 and drop support for 7
…Default undef all of them so it does nothing unless you enable.
Signed-off-by: William Yardley <[email protected]>
Release 14.0.0
Add an `enable_centos_release` parameter, defaulting to `false`, except on CentOS, where it defaults to `true`. If enabled on any OS in the RedHat family when `repos_ensure` is also disabled, it controls adding the `centos-release-rabbitmq` package (currently `centos-release-rabbitmq-38`) Fixes #1033 Closes #1032
Add `enable_centos_release` parameter
Signed-off-by: William Yardley <[email protected]>
Release 14.1.0
…fully dependent on an enablement variable now, with tests to verify that behavior.
puppet/systemd: allow 8.x
Add quorum queue auto-reconciliation parameter support
Release 14.2.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request (PR) description
This Pull Request (PR) fixes the following issues