Skip to content

Commit 65326bc

Browse files
ref(develop): Remove "option backed features" docs (#14295)
These should no longer be used and are currently being removed Part of [CORE-24: Remove "option backed" feature flags](https://linear.app/getsentry/issue/CORE-24/remove-option-backed-feature-flags)
1 parent 31df42a commit 65326bc

File tree

3 files changed

+3
-75
lines changed

3 files changed

+3
-75
lines changed

develop-docs/backend/application-domains/feature-flags/index.mdx

Lines changed: 3 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,6 @@ manager.add("organizations:onboarding", OrganizationFeature, FeatureHandlerStrat
2121

2222
# pass FeatureHandlerStrategy.INTERNAL if you don't plan to use options automator:
2323
manager.add("organizations:onboarding", OrganizationFeature, FeatureHandlerStrategy.INTERNAL)
24-
25-
# [DEPRECATED] pass FeatureHandlerStrategy.OPTIONS to use options automator:
26-
manager.add("organizations:onboarding", OrganizationFeature, FeatureHandlerStrategy.OPTIONS)
2724
```
2825

2926
The feature can be enabled with the following in your `sentry.conf.py`, usually located at `~/.sentry/`:
@@ -194,14 +191,9 @@ flags are then configured via `sentry.conf.py`. For Sentry's SaaS deployment,
194191
you have the choice of using an option backed rollout via Options Automator with Flagpole,
195192
or by writing a custom feature flag handler.
196193

197-
- [Flagpole](/backend/feature-flags/flagpole/) is Sentry's internal feature flagging library, allowing a feature
198-
with multiple target segments and condition filters to be defined in YAML within Options Automator.
199-
200-
- [Options based features](options-backed-features/) [DEPRECATED] allow a feature
201-
to be rolled out to a specific subset of LA orgs, a percentage of EA orgs,
202-
and/or a percentage of all orgs. These can be used in high scale situations, and are generally
203-
preferred over customer feature handlers. This strategy predates Flagpole, which is the new standard
204-
way to define an option-backed feature flag.
194+
[Flagpole](/backend/feature-flags/flagpole/) is Sentry's internal feature
195+
flagging library, allowing a feature with multiple target segments and
196+
condition filters to be defined in YAML within Options Automator.
205197

206198
## After launch (Graduation)
207199

develop-docs/backend/application-domains/feature-flags/options-backed-features.mdx

Lines changed: 0 additions & 52 deletions
This file was deleted.

src/middleware.ts

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -3574,10 +3574,6 @@ const DEVELOPER_DOCS_REDIRECTS: Redirect[] = [
35743574
from: '/feedback-architecture/',
35753575
to: '/application/feedback-architecture/',
35763576
},
3577-
{
3578-
from: '/feature-flags/options-backed-features/',
3579-
to: '/application/feature-flags/options-backed-features/',
3580-
},
35813577
{
35823578
from: '/options/',
35833579
to: '/backend/options/',
@@ -3788,14 +3784,6 @@ const DEVELOPER_DOCS_REDIRECTS: Redirect[] = [
37883784
from: '/api-server/application-domains/feature-flags/flagpole/',
37893785
to: '/develop/application-domains/feature-flags/flagpole/',
37903786
},
3791-
{
3792-
from: '/backend/feature-flags/options-backed-features/',
3793-
to: '/backend/application-domains/feature-flags/options-backed-features/',
3794-
},
3795-
{
3796-
from: '/api-server/application-domains/feature-flags/options-backed-features/',
3797-
to: '/develop/application-domains/feature-flags/options-backed-features/',
3798-
},
37993787
{
38003788
from: '/backend/options/',
38013789
to: '/backend/application-domains/options/',

0 commit comments

Comments
 (0)