Feature Request:
Currently, the DATABASE_URL environment variable is automatically added as a secret to the target Fly application when being attached by a Fly PostgreSQL cluster.
According to the PostgreSQL documentation (libpq environment variables), standard environment variables such as PGUSER, PGPASSWORD, PGHOST, PGPORT, and PGDATABASE are automatically read by libpq for PostgreSQL connections.
It would be beneficial if Fly.io also provided these standard environment variables alongside DATABASE_URL. This would improve compatibility with applications and tools that rely on libpq’s default behavior, allowing for more flexibility in connection configuration.
Would it be possible to support this feature?