Skip to content

ref(develop): Remove "option backed features" docs #14295

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 8, 2025
Merged

ref(develop): Remove "option backed features" docs #14295

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 3 additions & 11 deletions develop-docs/backend/application-domains/feature-flags/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,6 @@ manager.add("organizations:onboarding", OrganizationFeature, FeatureHandlerStrat

# pass FeatureHandlerStrategy.INTERNAL if you don't plan to use options automator:
manager.add("organizations:onboarding", OrganizationFeature, FeatureHandlerStrategy.INTERNAL)

# [DEPRECATED] pass FeatureHandlerStrategy.OPTIONS to use options automator:
manager.add("organizations:onboarding", OrganizationFeature, FeatureHandlerStrategy.OPTIONS)
```

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

- [Flagpole](/backend/feature-flags/flagpole/) is Sentry's internal feature flagging library, allowing a feature
with multiple target segments and condition filters to be defined in YAML within Options Automator.

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

## After launch (Graduation)

Expand Down
52 changes: 0 additions & 52 deletions develop-docs/backend/application-domains/feature-flags/options-backed-features.mdx
View file
Open in desktop

This file was deleted.

12 changes: 0 additions & 12 deletions src/middleware.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3574,10 +3574,6 @@ const DEVELOPER_DOCS_REDIRECTS: Redirect[] = [
from: '/feedback-architecture/',
to: '/application/feedback-architecture/',
},
{
from: '/feature-flags/options-backed-features/',
to: '/application/feature-flags/options-backed-features/',
},
{
from: '/options/',
to: '/backend/options/',
Expand Down Expand Up @@ -3788,14 +3784,6 @@ const DEVELOPER_DOCS_REDIRECTS: Redirect[] = [
from: '/api-server/application-domains/feature-flags/flagpole/',
to: '/develop/application-domains/feature-flags/flagpole/',
},
{
from: '/backend/feature-flags/options-backed-features/',
to: '/backend/application-domains/feature-flags/options-backed-features/',
},
{
from: '/api-server/application-domains/feature-flags/options-backed-features/',
to: '/develop/application-domains/feature-flags/options-backed-features/',
},
{
from: '/backend/options/',
to: '/backend/application-domains/options/',
Expand Down
Loading