-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
prevent operator from panic on invalid characters within Azure Eventhub-Storage path #3080
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Could you update the changelog? 🙏
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! Thanks for the contribution.
We should also open an issue for this, so it can be referenced in the Changelog
fix #3082 |
should i make a changelog entry within this PR? |
yes please, create an entry referring the issue 🙏 |
/run-e2e azure* |
479343c
to
1d4e317
Compare
…rage path Signed-off-by: Christian Leinweber <christian.leinweber@maibornwolff.de>
done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
Hello,
we facing an issue with a crashing keda operator if the storage path of the eventhub scaler contains invalid characters. In our case, this happened with a wrong encoded base64 secret.
this change prevents the operator from crashing The
url.parse
provide a valid readable error message with enough details for debugging, so I did not add additional information on it.Fixes: #3082