messaging-topology-operator
messaging-topology-operator copied to clipboard
unable to change user's import secret
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