From fa47e41600771949459e5835d54847b4cb9b0312 Mon Sep 17 00:00:00 2001 From: kenzoengineer Date: Thu, 12 Mar 2026 14:54:34 -0700 Subject: [PATCH] update flagpole docs to include new owner field --- .../feature-flags/flagpole.mdx | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/develop-docs/backend/application-domains/feature-flags/flagpole.mdx b/develop-docs/backend/application-domains/feature-flags/flagpole.mdx index 658b97ca9999e..b16bef2a47aa9 100644 --- a/develop-docs/backend/application-domains/feature-flags/flagpole.mdx +++ b/develop-docs/backend/application-domains/feature-flags/flagpole.mdx @@ -13,7 +13,9 @@ options: 'feature.organizations:is_sentry': created_at: '2024-06-01T00:00:00.000000' enabled: false - owner: hybrid-cloud + owner: + - team: hybrid-cloud + - email: foo@sentry.io segments: - conditions: - operator: in @@ -30,9 +32,6 @@ options: : The ISO 8601 datetime of when the feature was added to the config yaml. -`owner` - -: The team name or email of the user that owns this feature flag `enabled` [optional] @@ -42,6 +41,16 @@ options: : 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`. +### Owner + +`team` + +: The name of the team that owns this feature flag + +`email` [optional] + +: The email of the team that owns this feature flag + ### Segments `conditions`