It's not possible to specify using a secure connection when connecting with a postgres://user:password@host/database URL.
It doesn't look like JDBC allows for this. SQL Alchemy specifies optional parameters that might be useful.
Could we utilize something like postgres://user:pass@host/database?secure=true?
This matters because I have an application that passes the URL on the command line, and having the secure connection in the URL makes more sense than adding a --secure switch.
ideally yeah the connection string should take those parameters. Also, they PG* environment variables should be used
I tried to link my pull request, but apparently including the issue number didn't do the trick. #276
Should be closed with the merged pull. Thanks to @bryanburgers for the work.