Add multi team secret support to VaultBackend#65493
Open
stephen-bracken wants to merge 1 commit intoapache:mainfrom
Open
Add multi team secret support to VaultBackend#65493stephen-bracken wants to merge 1 commit intoapache:mainfrom
stephen-bracken wants to merge 1 commit intoapache:mainfrom
Conversation
5f9a21b to
13e0f1a
Compare
13e0f1a to
4c3c7e0
Compare
baraka-akeyless
added a commit
to baraka-akeyless/airflow
that referenced
this pull request
Apr 20, 2026
When core.multi_team is enabled, the secrets backend now looks up
secrets under {base_path}/{team_name}/{key} first, falling back to
a global path. Supports use_team_secrets_path and global_secrets_path
configuration options, matching the VaultBackend pattern from apache#65493.
Made-with: Cursor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add support for team scoped secrets to the VaultBackend secrets backend
related: #65372
If multi_team is enabled, the VaultBackend will now prefix each variable or connection id with the team name,
i.e.
{base_path}/{team_name}/{key}.If no key is found under the team specific secrets then a global path will be searched instead. This global path
will default to using the base path, but can also be prefixed e.g.
{base_path}/global/{key}or{base_path}/shared/{key}etc.Was generative AI tooling used to co-author this PR?