Add connection URL to connection details info card

This was tested in

Mysql connection details were hidden in

Mongodb connection details are displayed as

Postgresql connection details are displayed as

As per comment , if the connection url has special characters then they will be escaped.

The connection url can be copied by using the copy button to clipboard.

Hence closing this issue, since the scope is completed.

this should be all inside the input field independent of the size of the string and even though the user might not see it all at once, he can ‘navigate’ the text or copy it

for non-sharded 5-node psmdb cluster the connection URL could be that long:

mongodb://databaseAdmin:somePASSWORDDDD@mongodb-56u-rs0-0.mongodb-56u-rs0.my-special-place.svc.cluster.local:27017,mongodb-56u-rs0-1.mongodb-56u-rs0.my-special-place.svc.cluster.local:27017,mongodb-56u-rs0-2.mongodb-56u-rs0.my-special-place.svc.cluster.local:27017,mongodb-56u-rs0-3.mongodb-56u-rs0.my-special-place.svc.cluster.local:27017,mongodb-56u-rs0-4.mongodb-56u-rs0.my-special-place.svc.cluster.local:27017

(see the comment)

Is there a way to fit it to the current design?

Hi !

Questions regarding the ticket:

1. What is expected as connection URL for PXC? Here is the docs how to connect to a PXC cluster, it supposes to run percona-client and then use a command like mysql -h <cluster_name>-haproxy -uroot -p'<root_password>', so no URL is involved and I’m not sure what is expected here.

2. For PG (please correct me if I’m wrong) according to the docs we probably expect to provide the PGBOUNCER_URI as the mentioned Connection URL , so users are expected to run pg-client with this PGBOUNCER_URI

3. For PSMDB (please correct me if I’m wrong) according to the docs we probably expect the mongosh (mongodb://etc) url as the mentioned Connection URL. The mongosh url is built differently for sharded and non-sharded clusters, but the idea is the same - users are expected to run percona-client and then call mongosh "<connection URL>"