Connection String Examples

[Wombat45]

I'm trying to setup grate with a simple local Postgres db but am having trouble with the connection string I'm passing to grate. I think it would be helpful to include working examples in the docs.

I'm also curious what are the required and optional connstring args. Other than "Server" and "Database" I'm not sure what is expected. There are other tools like Teleport that can handle secure access to databases. It would be interesting to see what the connection string args are so that we could find out if grate supports teleport and tbot for authentication to the db.

[erikbra]

Hi, @Wombat45 - I tried keeping specification of the connection strings for grate as equal as what the underlying database connection provider expects. I don't know which environment you are running PostgreSQL in, etc.

For finding connection strings for databases I don't use a lot, I often refer to https://www.connectionstrings.com/ myself. From grate, we are using Npgsql to connect to PostgreSQL, so specifically for PostgresSQL, the options for connection strings should be explained here:

https://www.connectionstrings.com/npgsql/

[Wombat45]

Thank you this link is super helpful. I do think I discovered a bug though, I was able to connect with grate to a local postgresql db on my Mac using this cli command

grate -cs "Host=localhost;Port=5432;Database=database;Username=user;Password=password;" --env DEV --dt postgresql -v Trace --dryrun

however if I try and use the .rsp file to save this and run against I get errors that "Host" and "Port" keywords are not supported.
Keyword not supported: 'port'.
Keyword not supported: 'host'.
so I have to use "Server=" and not define the port in the .rsp like this and run grate @./grate_settings.rsp

-cs "Server=localhost;Database=database;User Id=user;Password=password;"
--env DEV
–dt postgresql
-v Trace
--dryrun

I get a network connection error from grate and it cannot connect.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server)

it seems that bc I can't pass the port in the -cs in the .rsp grate defaults to another port which is inaccessible