-
Notifications
You must be signed in to change notification settings - Fork 186
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
feat(elasticsearch): remove hard-coded port 9200, validate URL input #941
feat(elasticsearch): remove hard-coded port 9200, validate URL input #941
Conversation
Signed-off-by: clavinjune <24659468+clavinjune@users.noreply.github.com>
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.
Thank you for adding support for it and adding tests 🙏 Odigos should support any port and not only the default.
Add few minor comments
…instead and validate scheme & host, add more test cases Signed-off-by: clavinjune <24659468+clavinjune@users.noreply.github.com>
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 great.
Thank you for adding support for this and addressing the comments 🙏
please help to merge if all's good since I don't have any write access 🙇 |
This PR enables a flexible ES endpoints by removing hard-coded ES port in the endpoints section. This PR also sanitize/validate whether user input a valid URL or not by utilizing
url.Parse
. I'm wondering whether we do need to have a test or not sinceurl.Parse
function already have their own testPlease advise if we need more test cases
This PR will close #940