Add support to load enhanced feature flag

[Yuan Qu (yuanqu72)]

This pull request introduces support for loading enhanced feature flags (created via the dedicated feature flag resource endpoint) in the Azure App Configuration Provider, alongside several related improvements and breaking changes. Enhanced feature flags are now merged automatically with key-value based feature flags, and new selector types are introduced for flexible filtering. The minimum supported Python version and dependencies have also been updated.

Enhanced Feature Flag Support

• Enhanced feature flags created via the dedicated feature flag endpoint (FeatureFlagClient/FeatureFlag) are now automatically loaded and merged into the feature_management.feature_flags list when feature_flag_enabled=True. Enhanced feature flags take precedence over key-value based ones with the same name. No new options are required to opt in, and existing selectors filter both kinds. [1] [2] [3] [4] [5]

• Introduced the FeatureFlagSelector type for filtering enhanced feature flags by name, label, or tags. The feature_flag_selectors argument now accepts either a list of SettingSelector or FeatureFlagSelector instances (but not both), and this is reflected in the public API and documentation. [1] [2] [3] [4] [5] [6] [7]

Documentation and Usage

• Updated the README.md with usage examples and explanations for enhanced feature flags, including how to use selectors and how merging works. Added a section for package developers on running tests. [1] [2]

Dependency and Compatibility Updates

• Raised the minimum supported Python version to 3.10, dropping support for 3.7, 3.8, and 3.9, and updated the minimum dependency on azure-appconfiguration to >=1.10.0b1 for enhanced feature flag support. [1] [2]

Internal Implementation

• Refactored refresh logic to separately handle configuration settings and feature flag resources, ensuring correct and efficient merging and change detection for both key-value and enhanced feature flags. [1] [2] [3]

Other

• Updated asset tag in assets.json to reflect the new release.

[azure-pipelines]

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.

[Yuan Qu (yuanqu72)]

/azp run python - appconfiguration

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).