server properties change does not apply latest revision in the MSK cluster only creates a new revision

[aamirmushtaq]

Describe the Bug

When we create a new configuration by adding some parameters to the server_properties, the new configuration is created as a new revision in AWS but the same is not applied to the MSK cluster already launched. This is similar to what is reported here.

Expected Behavior

When adding / removing configuration from server properties, the new configuration is created as a new revision but the same is not automatically applied on the MSK cluster.

Steps to Reproduce

Modify properties that are being passed here. Plan the changes and apply. The new revision of the configuration is created but the same is not applied on the MSK cluster.

Screenshots

No response

Environment

No response

Additional Context

No response

[asvataa]

+1