PrithviBadiga commented on code in PR #65695:
URL: https://github.com/apache/airflow/pull/65695#discussion_r3133094076
##########
providers/yandex/docs/secrets-backends/yandex-cloud-lockbox-secret-backend.rst:
##########
@@ -251,6 +251,26 @@ To check the variable is correctly read from the Lockbox
Secret Backend, you can
$ airflow variables get my_variable
some_secret_data
+Multi-team lookup
+-----------------
+
+In multi-team mode, this backend looks for team-scoped secret names first and
falls back to the
+global secret name when a team-scoped secret is not found.
+
+For connections:
+
+* Team-scoped: ``{connections_prefix}/{team_name}/{conn_id}``
+* Global fallback: ``{connections_prefix}/{conn_id}``
Review Comment:
I updated the Lockbox backend to use a dedicated doubled separator between
the team and secret id, so team-scoped names are no longer ambiguous, and I
added matching detection to avoid resolving team-scoped secrets as global
secrets.
With the default separator, the format is now:
- team-scoped: `airflow/connections/team_a//my_db`
- global: `airflow/connections/my_db`
I also updated the tests and documentation accordingly.
--
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]
