Skip to content
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.

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

rabbitmq scaler reports that the username and password is bad - clarify what special characters means #6364

Closed
doctorpangloss opened this issue Nov 25, 2024 · 3 comments
Labels
bug Something isn't working stale All issues that are marked as stale due to inactivity

Comments

@doctorpangloss
Copy link
Contributor

Report

The notes for RabbitMQ Scaler say you can't use special characters in the username or password. Unfortunately the rabbitmq topology operator will create usernames and passwords with underscores. Does this count as a special character? I am getting bad username and password messages. It's kind of ridiculous that this is a problem

Expected Behavior

I should be able to use a username and password correctly

Actual Behavior

There is a vague warning about special characters in Keda and rabbitmq trigger auths

Steps to Reproduce the Problem

Logs from KEDA operator

No response

KEDA Version

2.15.1

Kubernetes Version

1.30

Platform

Other

Scaler Details

RabbitMQ

Anything else?

No response

@doctorpangloss doctorpangloss added the bug Something isn't working label Nov 25, 2024
@JorTurFer
Copy link
Member

Hello
Is this related with wrong escaping the password in the url? Are you willing to open a PR with the fix?

Copy link

stale bot commented Jan 27, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Jan 27, 2025
Copy link

stale bot commented Feb 4, 2025

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Feb 4, 2025
@github-project-automation github-project-automation bot moved this from To Triage to Ready To Ship in Roadmap - KEDA Core Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale All issues that are marked as stale due to inactivity
Projects
Status: Ready To Ship
Development

No branches or pull requests

2 participants