jedcunningham commented on code in PR #23307:
URL: https://github.com/apache/airflow/pull/23307#discussion_r864132429
##########
docs/helm-chart/production-guide.rst:
##########
@@ -52,6 +52,9 @@ configure the secret name:
.. _production-guide:pgbouncer:
+.. warning::
+ If you use `CeleryExecutor`, keep in mind that `resultBackendSecretName`
expects a url that starts with `db+postgresql://`, while `metadataSecretName`
expects `postgresql://` and wont work with `db+postgresql://`. You'll need to
create separate secrets with the correct scheme.
Review Comment:
```suggestion
If you use ``CeleryExecutor``, keep in mind that
``resultBackendSecretName`` expects a url that starts with
``db+postgresql://``, while ``metadataSecretName`` expects ``postgresql://``
and won't work with `db+postgresql://`. You'll need to create separate secrets
with the correct scheme.
```
##########
docs/helm-chart/production-guide.rst:
##########
@@ -52,6 +52,9 @@ configure the secret name:
.. _production-guide:pgbouncer:
+.. warning::
+ If you use `CeleryExecutor`, keep in mind that `resultBackendSecretName`
expects a url that starts with `db+postgresql://`, while `metadataSecretName`
expects `postgresql://` and wont work with `db+postgresql://`. You'll need to
create separate secrets with the correct scheme.
Review Comment:
```suggestion
If you use ``CeleryExecutor``, keep in mind that
``resultBackendSecretName`` expects a url that starts with
``db+postgresql://``, while ``metadataSecretName`` expects ``postgresql://``
and won't work with ``db+postgresql://``. You'll need to create separate
secrets with the correct scheme.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
