Skip to content

Commit 7d0429f

Browse files
feat(flagpole): Update flagpole documentation with new owner field (#16918)
<!-- Use this checklist to make sure your PR is ready for merge. You may delete any sections you don't need. --> ## DESCRIBE YOUR PR The owner field has been changed to separate out the team and email fields. This updates the documentation to reflect this change. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [x] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [x] Checked Vercel preview for correctness, including links - [x] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs)
1 parent b81942c commit 7d0429f

1 file changed

Lines changed: 13 additions & 4 deletions

File tree

  • develop-docs/backend/application-domains/feature-flags

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

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,9 @@ options:
1313
'feature.organizations:is_sentry':
1414
created_at: '2024-06-01T00:00:00.000000'
1515
enabled: false
16-
owner: hybrid-cloud
16+
owner:
17+
- team: hybrid-cloud
18+
- email: foo@sentry.io
1719
segments:
1820
- conditions:
1921
- operator: in
@@ -30,9 +32,6 @@ options:
3032

3133
: The ISO 8601 datetime of when the feature was added to the config yaml.
3234

33-
`owner`
34-
35-
: The team name or email of the user that owns this feature flag
3635

3736
`enabled` [optional]
3837

@@ -42,6 +41,16 @@ options:
4241

4342
: A wrapper around a list of conditions, acting as a logical grouping of customers/entities to enable the feature flag for. Segments allow you to create `OR` operations with other segments, meaning at least one segment must evaluate to `True` for a feature to be granted. If an empty segments list is provided, the feature will evaluate to `False`.
4443

44+
### Owner
45+
46+
`team`
47+
48+
: The name of the team that owns this feature flag
49+
50+
`email` [optional]
51+
52+
: The email of the team that owns this feature flag
53+
4554
### Segments
4655

4756
`conditions`

0 commit comments

Comments
 (0)