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

Better exception message for Could not parse URI #1016

Merged
merged 1 commit into from
Apr 17, 2020

Conversation

alexander-schranz
Copy link
Contributor

@alexander-schranz alexander-schranz commented Apr 9, 2020

Not sure what the current lowest supported version is. Please change the target branch or ping me.

Most users run into this exception when they configure the URI false but mostly we are not sure if the ENV environment don't work or if they just really configured a not parse able url. So it would be great to output the given value in the exception message also to improve developer experience.

@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@ezimuel
Copy link
Contributor

ezimuel commented Apr 17, 2020

@alexander-schranz thanks for this PR. I think I need to merge this also in 6.x, 7.x and master. I'll start releasing next week with 7.7.

@ezimuel ezimuel added this to the 7.7 milestone Apr 17, 2020
@ezimuel ezimuel merged commit 80fe9b1 into elastic:5.x Apr 17, 2020
@ezimuel
Copy link
Contributor

ezimuel commented Apr 17, 2020

I merged in 5.x, 6.x, 7.x and master. Ready for 7.7 to be released.

@alexander-schranz alexander-schranz deleted the patch-1 branch April 17, 2020 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants