ability to use postgresql:// in addition to postgres://
When initially deploying I used cloudnative-pg to deploy a postgres database.
cloudnative-pg provides a connection string which starts with postgresql://, it would be nice if mattermost also recognized this url schema and used it the same as postgres. This would help with help to allow for full automation around deployment as it would eliminate the need to edit the provided connectionstring.
I'm deploying via gitops using argocd, which lets me in general just delete a namespace, and everything will come back. Without recognizing postgresql I'll have to start looking into using an initContainer or something and perhaps add in rbac to allow for modifying secrets. It is probably doable, but if other folks might use various ways to deploy postgres, it may be there will be lots of folks who would benefit by recognizing 'postgresql' as a valid schema
e.g.:
postgresql://app:[email protected]:5432/app?sslmode=disable&connect_timeout=10
Here's what a google search says on the matter:
The postgres:// and postgresql:// URL schemes are functionally equivalent and both refer to the same database protocol used to connect to a PostgreSQL database server. The difference lies solely in the naming convention used in the URL scheme.
postgresql:// is the officially recognized and preferred scheme for PostgreSQL database connections, reflecting the project's official name.
However, postgres:// is a widely accepted and commonly used alias, often favored for its brevity and ease of pronunciation.
This usage is so prevalent that many tools, libraries, and documentation accept both schemes interchangeably.
In practice, when connecting to a PostgreSQL database, you can use either postgres:// or postgresql:// in your connection string, and the connection will be established successfully as long as the rest of the URL (host, port, database name, credentials) is correct. The choice between the two is largely a matter of preference or convention within a specific project or organization.