Configuration for Deprecated Features in RabbitMQ Not Reflected in UI or CLI

Products

• VMware Tanzu Data Suite
• RabbitMQ
• Support Only for OpenSource RabbitMQ
• VMware Tanzu RabbitMQ

Issue/Introduction

In RabbitMQ version 4.1.0, administrators can define behavior for deprecated features using the "deprecated_features" configuration block. However, after setting such configurations (e.g., disabling specific deprecated behaviors), the changes are not reflected in the RabbitMQ Management UI or CLI tools. 

Environment

RabbitMQ 4.1.0

Cause

This issue is due to the current implementation of RabbitMQ’s deprecated feature tracking system. While the configuration is correctly parsed and applied by the server, the internal tracking system does not expose the current active state (enabled/disabled) of these deprecated features in the Management UI or through the CLI tools.

The listing of deprecated features only shows the deprecation phase (e.g., "deprecated", "to be removed", etc.), but not whether the feature is permitted or denied via configuration.

Resolution

This issue is resolved in upcoming RabbitMQ 4.2.0 release, where an additional column is added to understand about the "current cluster configuration" for the deprecated features.

PR Reference