Skip to content

Allow tagged (e.g. encrypted:...) values for more rabbitmq.conf keys (backport #15808)#15810

Merged
michaelklishin merged 2 commits intov4.3.xfrom
mergify/bp/v4.3.x/pr-15808
Mar 23, 2026
Merged

Allow tagged (e.g. encrypted:...) values for more rabbitmq.conf keys (backport #15808)#15810
michaelklishin merged 2 commits intov4.3.xfrom
mergify/bp/v4.3.x/pr-15808

Conversation

@mergify
Copy link
Copy Markdown

@mergify mergify Bot commented Mar 23, 2026

When the support for tagged values in rabbitmq.conf was introduced #11989, not all candidate keys were immediately marked as supporting these new value types.

This PR updates a few more sensitive rabbitmq.conf keys to support encrypted:... values.

References #11989, #15807.


This is an automatic backport of pull request #15808 done by [Mergify](https://mergify.com).

…keys

When the support for tagged values in `rabbitmq.conf` was introduced,
not all candidate keys were updated to include it.

This PR updates a few more sensitive `rabbitmq.conf` keys
to support `encrypted:...` values.

References #11989.

(cherry picked from commit e07cdf9)
(cherry picked from commit b9325dc)
@michaelklishin michaelklishin added this to the 4.3.0 milestone Mar 23, 2026
@michaelklishin michaelklishin merged commit 62321de into v4.3.x Mar 23, 2026
354 of 356 checks passed
@michaelklishin michaelklishin deleted the mergify/bp/v4.3.x/pr-15808 branch March 23, 2026 21:07
michaelklishin added a commit that referenced this pull request Mar 23, 2026
Allow tagged (e.g. `encrypted:...`) values for more `rabbitmq.conf` keys (backport #15808) (backport #15810)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant