dstandish commented on code in PR #24929:
URL: https://github.com/apache/airflow/pull/24929#discussion_r917024134
##########
docs/helm-chart/production-guide.rst:
##########
@@ -59,7 +59,7 @@ 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 won't work with
``db+postgresql://``. You'll need to create separate secrets with the correct
scheme.
+ If you use ``CeleryExecutor`` and Airflow version < ``2.4``, 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. For Airflow version >= ``2.4`` it is possible
not to specify the secret again, as Airflow will use ``sql_alchemy_conn``
(specified in ``metadataSecret``) with a db+ scheme prefix by default.
Review Comment:
```suggestion
If you use ``CeleryExecutor`` and Airflow version < ``2.4``, 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. For Airflow version >= ``2.4`` it is possible
to omit the result backend secret, as Airflow will use ``sql_alchemy_conn``
(specified in ``metadataSecret``) with a db+ scheme prefix by default.
```
--
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]
