Skip to content

Commit df24e81

Browse files
committed
Update feature-management-python-reference.md
1 parent 786aa69 commit df24e81

File tree

1 file changed

+6
-12
lines changed

1 file changed

+6
-12
lines changed

articles/azure-app-configuration/feature-management-python-reference.md

Lines changed: 6 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Here are some of the benefits of using Python feature management library:
3737
* Low barrier-to-entry
3838
* Supports JSON feature flag setup
3939
* Feature Flag lifetime management
40-
* Configuration values can change in real-time; feature flags can be consistent across the entire request
40+
* Configuration values can change in real-time; feature flags can be consistent across the entire requestf
4141
* Simple to Complex Scenarios Covered
4242
* Toggle on/off features through declarative configuration file
4343
* Dynamically evaluate state of feature based on call to server
@@ -48,18 +48,16 @@ Here are some of the benefits of using Python feature management library:
4848
Feature flags are composed of two parts, a name and a list of feature-filters that are used to turn on the feature.
4949

5050
### Feature Filters
51-
Feature filters define a scenario for when a feature should be enabled. When a feature is evaluated for whether it is on or off, its list of feature filters is traversed until one of the filters decides the feature should be enabled. At this point, the feature is considered enabled and traversal through the feature filters stops. If no feature filter indicates that the feature should be enabled, it's considered disabled.
51+
Feature filters define a scenario for when a feature should be enabled. When a feature is evaluated for whether it is on or off, its list of feature filters is traversed until one of the filters decides the feature should be enabled. At this point, the feature is considered enabled and traversal through the feature filters stops. If no feature filter indicates that the feature should be enabled, it will be considered disabled.
5252

53-
As an example, a Microsoft Edge browser feature filter could be designed. This feature filter would activate any features it's attached to as long as an HTTP request is coming from Microsoft Edge.
53+
As an example, a Microsoft Edge browser feature filter could be designed. This feature filter would activate any features attached to it, as long as an HTTP request is coming from Microsoft Edge.
5454

5555
### Feature Flag Configuration
5656

5757
A Python dictionary is used to define feature flags. The dictionary is composed of feature names as keys and feature flag objects as values. The feature flag object is a dictionary that contains an `EnabledFor` key. The `EnabledFor` key is a list of feature filters that are used to determine if the feature should be enabled
5858

5959
### Feature Flag Declaration
6060

61-
:::zone target="docs" pivot="stable-version"
62-
6361
The feature management library supports json as a feature flag source. Below we have an example of the format used to set up feature flags in a json file.
6462

6563
```json
@@ -162,10 +160,6 @@ A `requirement_type` of `All` changes the traversal. First, if there are no filt
162160

163161
In the above example, `FeatureW` specifies a `requirement_type` of `All`, meaning all of its filters must evaluate to true for the feature to be enabled. In this case, the feature is enabled for 50% of users during the specified time window.
164162

165-
### Python Feature Management schema
166-
167-
In previous versions, the primary schema for the feature management library was the [`.NET feature management schema`](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureManagement.v2.0.0.schema.json). Starting from v2.0.0b1, new features including variants and telemetry won't be supported for the .NET feature management schema.
168-
169163
## Consumption
170164

171165
The basic form of feature management is checking if a feature flag is enabled and then performing actions based on the result. This is done through `FeatureManager`'s `is_enabled` method.
@@ -214,7 +208,6 @@ Each of the built-in feature filters has its own parameters. Here's the list of
214208
This filter provides the capability to enable a feature based on a time window. If only `End` is specified, the feature is considered on until that time. If only `Start` is specified, the feature is considered on at all points after that time.
215209

216210
```json
217-
218211
"client_filters": [
219212
{
220213
"name": "Microsoft.TimeWindow",
@@ -223,8 +216,7 @@ This filter provides the capability to enable a feature based on a time window.
223216
"End": "Mon, 01 Jul 2019 00:00:00 GMT"
224217
}
225218
}
226-
]
227-
219+
]
228220
```
229221

230222
### Microsoft.Targeting
@@ -609,6 +601,8 @@ When a feature flag is evaluated and telemetry is enabled, the feature manager w
609601
| `Variant` | The assigned variant. |
610602
| `VariantAssignmentReason` | The reason why the variant is assigned. |
611603

604+
:::zone-end
605+
612606
## Next steps
613607

614608
To learn how to use feature flags in your applications, continue to the following quickstarts.

0 commit comments

Comments
 (0)