Fix bug in Mega Components with DB URL

[rkeene]

This change fixes a bug where addSubjectAlternativeToHosts cannot work with a URL generated and stored in MC_PSQL_DB_URL because it passes the protocol to openssl s_client ... -starttls <protocol> and postgres is a valid STARTTLS protocol option while postgresql is not.

---

Note

Low Risk
Single scheme string in Pulumi env output; behavior change is limited to URL parsing for STARTTLS and standard drivers accept postgres://.

Overview

Summary

Mega Components host SAN automation (addSubjectAlternativeToHosts) reads the URL scheme and passes it to openssl s_client -starttls. URLs built as postgresql:// produced an invalid STARTTLS protocol; postgres:// matches what OpenSSL expects so TLS cert discovery and /etc/hosts updates work for database connections.

Related Issues

None

Changes Made

• MC_PSQL_DB_URL from buildDatabaseEnvVars uses the postgres:// scheme instead of postgresql:// (same host, credentials, port, and sslmode=require)

Testing

None

Breaking Changes

None (both schemes are widely accepted PostgreSQL connection URLs; only consumers that required the literal postgresql prefix would differ)

^{Reviewed by Cursor Bugbot for commit 9d33186. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud