Skip to content

Commit a086a1c

Browse files
chore(flagpole): Adds docs for flagpole feature removal
1 parent bd8d23b commit a086a1c

File tree

1 file changed

+7
-1
lines changed
  • develop-docs/backend/application-domains/feature-flags

1 file changed

+7
-1
lines changed

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

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -228,7 +228,7 @@ options:
228228
rollout: 100
229229
```
230230

231-
You can push your feature option to your local devserver using the following `getsentry` CLI command:
231+
You can push your feature option to your local devserver using the following `getsentry configoptions` CLI command:
232232

233233
```bash
234234
getsentry configoptions -f <path>/<to>/<your>/<config>.yml -l DEBUG patch
@@ -240,3 +240,9 @@ you remove the feature option.
240240

241241
To unset your feature, comment out or remove your feature config from the
242242
`option` object, and rerun the `getsentry configoptions` command above.
243+
244+
## Removing Flagpole features
245+
Because our options automator CI relies on the feature definitions in both Sentry and GetSentry, flags must be removed in a specific order to avoid causing test failures:
246+
1. Remove all flag checks from the codebase and set a default value of `True` for the flag.
247+
2. Once all flag checks have been removed and the changes have been deployed to all environments, remove the feature flag config from options automator.
248+
3. Remove the [feature registration](#rolling-out-a-new-flagpole-feature) from GetSentry or Sentry.

0 commit comments

Comments
 (0)