You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: develop-docs/application/feature-flags/flagpole.mdx
+1-10Lines changed: 1 addition & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -160,7 +160,7 @@ To see the latest context properties available, check out the repo-specific cont
160
160
161
161
## Rolling out a new Flagpole feature
162
162
163
-
Creating a new Flagpole Feature is currently a 3 step process:
163
+
Creating a new Flagpole Feature is currently a 2 step process:
164
164
1. Register a new feature in Sentry's `temporary.py` file or GetSentry's `features.py` file with the Flagpole strategy:
165
165
```python
166
166
features.add(
@@ -176,8 +176,6 @@ features.add(
176
176
feature.<feature_scope>:<feature_name>
177
177
```
178
178
179
-
3. Add the feature name to the `flagpole.flagpole_only_features` list in sentry-options-automator's default [`app.yaml`](https://github.com/getsentry/sentry-options-automator/blob/483737d45dbc68253e926c3f860b5ae33111697b/options/default/app.yaml#L219) file, omitting the `feature.` prefix.
180
-
181
179
Once the option change is deployed, the feature checks will immediately be active in all environments and regions.
182
180
183
181
_Note:_ The feature config should not be merged until the registration commit in step 1 has been fully deployed to all target environments. This is because Options Automator will fail to push options to any environments missing the option registration.
@@ -194,9 +192,6 @@ file should contain a top-level `options` object containing your feature object,
194
192
and a `flagpole.flagpole_only_features` list option containing the name of the
195
193
feature you want to test, without the `feature.` prefix:
0 commit comments