-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
proposed updates for flagsmith integration docs #14225
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.
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
### Set Up Evaluation Tracking | ||
|
||
Flagsmith recommends using a OpenFeature SDK and [Flagsmith Provider](https://openfeature.dev/ecosystem?instant_search%5Bquery%5D=flagsmith&instant_search%5BrefinementList%5D%5Btype%5D%5B0%5D=Provider) to evaluate feature flags. To track these evaluations, visit one of our supported languages pages for OpenFeature: | ||
* [JavaScript](/platforms/javascript/configuration/integrations/openfeature/) | ||
* [Python](/platforms/python/integrations/openfeature/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only changed content for this file. The rest can stay the same, other than sidebar_order: 1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Flagsmith Integration: Missing Save Step
The Flagsmith integration documentation contains two issues in the "Set Up Change Tracking" section:
- Step 1 incorrectly instructs users to "Select Generic in the dropdown that says 'Select a provider'". This should either be "Select Flagsmith" or include an explanation if "Generic" is the intended selection for Flagsmith integration.
- Step 3, "Set the Signing Secret", omits an explicit instruction to save the configuration, only stating "Once saved" without detailing the save action.
docs/organization/integrations/feature-flag/flagsmith/index.mdx#L26-L37
sentry-docs/docs/organization/integrations/feature-flag/flagsmith/index.mdx
Lines 26 to 37 in dd8de37
- One webhook secret can be registered per provider type. | |
- Select Generic in the dropdown that says "Select a provider". | |
2. **Register the webhook URL**. | |
- Go to your Flagsmith project dashboard and navigate to the `/project/:projectid/integrations` page, which can be found by clicking "Integrations" on the top navigation bar. | |
- Find the Sentry option, and click "Add Integration", which will open a modal. | |
- Select the Environment from which flag change events will trigger. | |
- Copy the provided Sentry webhook URL and paste it into "Webhook URL" in the Flagsmith "Sentry Integration" modal. | |
3. **Set the Signing Secret**. | |
- Still in the Flagsmith "Sentry Integration" modal, type in any string between 10 and 60 characters to use as your authorization token ("secret"). | |
- Copy the authorization token from the previous step and paste it into the input box next to "Secret" in Sentry settings. | |
Once saved, Sentry will now accept and authenticate all inbound hooks to your organization's feature flag webhook endpoint. |
BugBot free trial expires on July 22, 2025
You have used $0.00 of your $50.00 spend limit so far. Manage your spend limit in the Cursor dashboard.
Was this report helpful? Give feedback by reacting with 👍 or 👎
Bundle ReportChanges will increase total bundle size by 860.64kB (4.08%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-client-array-pushAssets Changed:
view changes for bundle: sentry-docs-server-cjsAssets Changed:
|
Merge into #14126 (external PR)