- Added a
Recurrenceoption to theTimeWindowFilterto support recurring time window. This enables scenarios where a feature flag is activated based on a recurrence pattern, such as every day after 5 PM or every Friday. See Enable features on a schedule for more details. - Added
VariantAssignmentPercentageandDefaultWhenEnabledproperties to telemetry when telemetry is published to Azure Monitor. This allows you to track the percentage of users assigned to each variant and the default variant when the feature flag is enabled.VariantAssignmentPercentageis the the total percentage of users assigned to the variant, even across multiple allocations.DefaultWhenEnabledis the variant that is assigned when the feature flag is enabled and no other variant is assigned. - Added
TargetingSpanProcessorthat can be used to add the Targeting Id to Spans. Requiresazure-monitor-events-extensionto be installed.
-
Added support for variant feature flags. A variant feature flag is an enhanced feature flag that supports multiple states or variations. While it can still be toggled on or off, it also allows for different configurations, ranging from simple primitives to complex JSON objects. Variant feature flags are particularly useful for feature rollouts, configuration rollouts, and feature experimentation (also known as A/B testing).
For more information, see the feature reference document.
-
Added support for telemetry in feature flags. Telemetry allows you to track how your features are being used. It provides insights into the effectiveness of your feature flags and helps you make data-driven decisions. Telemetry is particularly useful for feature experimentation (also known as A/B testing) and feature rollouts.
An example is available to demonstrate how to use the new Telemetry in Python See the example in the examples folder.
- Fixed a bug where users exactly at the 100th percentile in allocation were incorrectly assigned a reason of
Noneinstead ofAllocationin feature evaluation telemetry.
- Added support for including
VariantAssignmentPercentageandDefaultWhenEnabledproperties to telemetry when telemetry is enabled and published to Azure Monitor.
- Added support for variant feature flags. A variant feature flag is an enhanced feature flag that supports multiple states or variations. While it can still be toggled on or off, it also allows for different configurations, ranging from simple primitives to complex JSON objects. Variant feature flags are particularly useful for feature rollouts, configuration rollouts, and feature experimentation (also known as A/B testing).
For more information, see the feature reference document.
- Added support for telemetry in feature flags. Telemetry is a powerful feature that allows you to track how your feature flags are being used. It provides insights into the effectiveness of your feature flags and helps you make data-driven decisions. Telemetry is particularly useful for feature experimentation (also known as A/B testing) and feature rollouts.
An example is available to demonstrate how to use the new Telemetry in Python See the example in the examples folder.
GA Release of the feature management support for Python. Note that, version 1.2.0 or later of azure-appconfiguration-provider is required for loading feature flags from Azure App Configuration.
- Loading of feature flags from a dictionary.
- Support for basic feature flags with boolean states.
- Support for feature filters including built-in filters
TimeWindowFilterandTargetingFilter.
Initial release of the feature management support for Python. Note that, version 1.2.0 or later of azure-appconfiguration-provider is required for loading feature flags from Azure App Configuration.
- Loading of feature flags from a dictionary.
- Support for basic feature flags with boolean states.
- Support for feature filters including built-in filters
TimeWindowFilterandTargetingFilter.