New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

unable to change user's import secret #924

Open

KyriosGN0 opened this issue Jan 1, 2025 · 0 comments

Labels

bug

KyriosGN0 commented Jan 1, 2025

Describe the bug

when changing the name of the import secret in a user CR, the message topology update doesn't update the user itself

To Reproduce

Steps to reproduce the behavior:

create a user with a import secret (our name was -user-credentials)
create a new secret with a required password and username fields
change the import secret param in the user cr
try to login with the new user, fails

Expected behavior
rmq will use the password in the new secret

Version and environment information

Messaging Topology Operator: [1.15.0]
RabbitMQ: [e.g. 3.13.7]
RabbitMQ Cluster Operator: [1.15.0]
Kubernetes: [1.30.0]
Cloud provider or hardware configuration: GKE

Additional context

the new secret had more fields then required if that's a problem

KyriosGN0 added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment