Appconfig provider ff endpoint - #48700
Merged
Matthew Metcalf (mrm9084) merged 8 commits intoAug 25, 2026
Merged
Conversation
…in the provider Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Yuan Qu (yuanqu72)
requested review from
Avani Gupta (avanigupta),
Jimmy Campbell (jimmyca15) and
Matthew Metcalf (mrm9084)
as code owners
August 24, 2026 06:50
|
Azure Pipelines: 10 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
github-actions
Bot
added
the
App Configuration
Member
Author
|
/azp run python - appconfiguration |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
…e sentinel/watch-key logic and timing Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
Author
|
/azp run python - appconfiguration |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
…wn my_json key and looking up Beta by id instead of a fragile index Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Matthew Metcalf (mrm9084)
requested changes
Aug 24, 2026
| """ | ||
| if selectors is None: | ||
| return [SettingSelector(key_filter="*")], [FeatureFlagSelector(name_filter="*")] | ||
| if not selectors: |
There was a problem hiding this comment.
Is this needed as a special case? If the lists are empty we should just be processing nothing then returning two empty lists.
Member
Author
There was a problem hiding this comment.
We are just returning two empty lists early here. Otherwise, the next two lines will throw error when we call next() on an empty list:
selectors_iter = iter(selectors)
first_selector = next(selectors_iter)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Matthew Metcalf (mrm9084)
approved these changes
Aug 25, 2026
Matthew Metcalf (mrm9084)
merged commit Aug 25, 2026
7b0e562
into
Azure:appconfig-ff-endpoint-preview
2 of 3 checks passed
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
2 participants
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.
This pull request introduces support for automatically loading enhanced feature flags (created via the dedicated feature flag resource endpoint) alongside existing key-value based feature flags in the Azure App Configuration Provider for Python. Enhanced feature flags are now merged into the same
feature_management.feature_flagslist, taking precedence over key-value based flags with the same name. The release also raises the minimum supported Python version to 3.10 and updates dependencies. Documentation and API have been updated to reflect these changes.Enhanced Feature Flag Support:
FeatureFlagClient/FeatureFlagresource endpoint are now loaded and merged automatically with key-value based feature flags whenfeature_flag_enabled=True. Resource-based feature flags take precedence if names overlap, and existing selectors filter both types. No newload()options are required. [1] [2]FeatureFlagSelectoras a dedicated selector type for filtering enhanced feature flags by name, label, or tags. API signatures forfeature_flag_selectorsnow accept either a list ofSettingSelectororFeatureFlagSelector, but not both. [1] [2] [3] [4] [5] [6] [7]Codebase and API Updates:
Dependency and Compatibility Changes:
azure-coreandazure-appconfigurationto support enhanced feature flags. [1] [2]Other: