importCredentialsSecret confusion #1068
Description
I understand after more experimentation that I was wrong in my comment on #408 (#408 (comment)) and that the username (and the password) from the secret is respected, and that without the secret and the importCredentialsSecret. I must have had some weird situation where I changed the secret's password value and thus I didn't realize that RabbitMQ's Messaging Topology Operator had correctly created the user with the correct password. I apologize for my confusing comment that must have come across as spam. I misunderstood the comment from @MirahImage that said:
Hi @kriswuollett, thanks for opening this issue. This is intended behavior, as the operator needs a secret over which it has ownership for design reasons. We are aware this leads to some duplication.
I misunderstood this as saying that the weird behavior that I was seeing whereby my username was respected but the password was not and was auto-generated was intended behavior. Clearly that isn't the case and I must have done something wrong, but I am opening this ticket to clear the record.
As others have suggested, maybe it would be nice to indicate clearly in the userPreDefinedCreds.yaml documentation that the secret used is not the secret which the user is importing from, but instead, another secret named USER-PROVIDED-USERNAME + "-user-credentials". I would be happy to make this update if you think that it would be useful.