The various database_url settings are consumed via GCP secrets:
https://github.com/codecov/k8s-v2/blob/cb63c4ed98bde7bb2d22d8f6d3ae6564fa5aa83d/charts/codecovWorker/conf/env.yaml#L55-L61
For example, sm://codecov-dev/codecov_staging_db_url_celery.
Some (most?) of these secrets currently begin with postgres://, but this is blocking an upgrade of the sqlalchemy dependency which switched to postgresql:// and has removed backwards compatibility support in v 1.4.0.
For that reason, I would like to switch over those secrets to postgresql://.
Lets start with staging first, and verify that both older and newer versions of the dependency handle that prefix correctly, before also rolling that change out to production and DEC.
The various
database_urlsettings are consumed via GCP secrets:https://github.com/codecov/k8s-v2/blob/cb63c4ed98bde7bb2d22d8f6d3ae6564fa5aa83d/charts/codecovWorker/conf/env.yaml#L55-L61
For example,
sm://codecov-dev/codecov_staging_db_url_celery.Some (most?) of these secrets currently begin with
postgres://, but this is blocking an upgrade of thesqlalchemydependency which switched topostgresql://and has removed backwards compatibility support in v1.4.0.For that reason, I would like to switch over those secrets to
postgresql://.Lets start with staging first, and verify that both older and newer versions of the dependency handle that prefix correctly, before also rolling that change out to production and DEC.