@@ -21,9 +21,6 @@ manager.add("organizations:onboarding", OrganizationFeature, FeatureHandlerStrat
2121
2222# pass FeatureHandlerStrategy.INTERNAL if you don't plan to use options automator:
2323manager.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
2926The 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,
194191you have the choice of using an option backed rollout via Options Automator with Flagpole,
195192or 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
0 commit comments