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

In case of using a connection url the shell connection fails. #561

Open
mjaksa opened this issue Apr 9, 2021 · 2 comments
Open

In case of using a connection url the shell connection fails. #561

mjaksa opened this issue Apr 9, 2021 · 2 comments

Comments

@mjaksa
Copy link

mjaksa commented Apr 9, 2021

Expected Behavior

Shell tool should connect without an error.

Current Behavior

Shell throws the following error: "FailedToParse: Database name cannot have reserved characters for mongodb:// URL: mongodb://username:password@host:port//opt/meteor/dist/bundle/some_ca.pem?authSource=admin&replicaSet=some_replication_set&tls=true&tlsCAFile=/opt/meteor/dist/bundle/some_ca.pem"

Possible Solution

Parsing of the connection string for the shell is bugy.
As you can see the parsed connection string hase the .pem file path where the DB name should be.

Steps to Reproduce (for bugs)

  1. use the connection url in the following format to create a connection: mongodb://some_user:password@host:port/test?authSource=admin&replicaSet=some_replication_set&tls=true&tlsCAFile=some_ca.pem
  2. after connecting go to tools/shell and the error shows up

Context

Unable to use the shell tool.

Your Environment

Runs from the offical docker image on an openshift cloud.
Browser: Google Chrome Version 87.0.4280.88 (Official Build) (64-bit)

@mjaksa
Copy link
Author

mjaksa commented Apr 15, 2021

i made a fix for this. If you want i can provide it.

@rsercano
Copy link
Member

Hi @mjaksa yes please that would be great, if you can provide the PR, I would be happy to check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants