-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat: Feature gate session replay controls using available_product_features #19401
Conversation
@@ -41,7 +41,7 @@ import { NodeKind } from './queries/schema' | |||
|
|||
export type Optional<T, K extends string | number | symbol> = Omit<T, K> & { [K in keyof T]?: T[K] } | |||
|
|||
// Keep this in sync with backend constants (constants.py) | |||
// Keep this in sync with backend constants/features/{product_name}.yml |
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.
Feels like another thing we could automatically publish from billing so we don't have to manually keep it in sync.
Size Change: 0 B Total Size: 2 MB ℹ️ View Unchanged
|
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.
Perhaps I've missed something but this doesn't feel like something we should control with billing features...
Why would we only offer it if you are subscribed? Even on a free tier it makes a lot of sense and keeps people using it. If you are thinking of upgrading but are worried about cost, maybe the thing you would do first is add the controls before upgrading.
Similarly if you downgrade but had some testings configured, you're now stuck with whatever setting you had...
Unless there is really strong reasoning why we would do this, I would personally vote to keep it as a flagged feature and gradually roll out to everyone. If we want to limit to only new users - feature flag, keeps it simple and allows us to conditionally add more legacy users for example as a tool for customer success.
@benjackwhite with the new plans it won't only be offered when you are sub'd. It'll be available on the free plans too. (you can peek the plans here https://github.com/PostHog/billing/pull/437/files) BUT because we want to pair the rollout of more sensible pricing with the rollout of the controls (ie. you get these controls, but you also have a lower free tier to accommodate that), that means that existing plans (with the higher free tier) won't get access to the controls. We know what plans they are on from billing, so adding the feature gating via billing makes a lot of sense. Once we see how much people use these and what the impacts are we will consider migrating everyone to the new plans - until then if people want them they can be put on the new plans manually. |
frontend/src/scenes/settings/project/SessionRecordingSettings.tsx
Outdated
Show resolved
Hide resolved
You can now control whether the settings show either with the feature flag or by setting individual settings: Screen.Recording.2023-12-21.at.1.33.46.PM.mp4 |
This can go in now, no need to wait for billing launch since we are still looking for the flag value. |
📸 UI snapshots have been updated3 snapshot changes in total. 0 added, 3 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated3 snapshot changes in total. 0 added, 3 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated2 snapshot changes in total. 0 added, 2 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated3 snapshot changes in total. 0 added, 3 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated4 snapshot changes in total. 0 added, 4 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the |
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.
Happy to defer to your judgement. Still feels weird that we would need both available features and feature flag but if it works, it works.
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.
There aren't many people with the flag on, so we can follow up by checking price impact of moving them to the new plans to get to a place where we can remove the flag but there's no rush for that
…atures (#19401) * feature gate session replay control using available_product_features * separate out feature checks * refine the separate feature checks * Update query snapshots * Update UI snapshots for `chromium` (2) * Update query snapshots * Update UI snapshots for `chromium` (2) * Update UI snapshots for `chromium` (2) * Update UI snapshots for `chromium` (2) * Update UI snapshots for `chromium` (2) * Update UI snapshots for `chromium` (2) * Update UI snapshots for `chromium` (2) --------- Co-authored-by: Bianca Yang <[email protected]> Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
* master: (94 commits) feat: Add cta on billing for >20k annual spend customers (#19508) refactor(temporal/squash): Support flat person override table in squash workflow (#19347) fix(surveys): remove link in user interview template (#19584) feat: populate plugin capabilities on install and edit (#19188) chore: Make plugin-server ignore deleted plugin configs (#18444) chore: Add Flutter feature flags snippets (#19563) fix(bi): fixed some of the query duplications (#19573) fix: assume typeless series nodes are of type events node (#19550) chore(deps): bump chromaui/action from 1 to 10 (#19560) fix(trends): fix breakdowns persons label (#19534) fix(trends): fix breakdown legend (#19533) feat: incremental updates for mobile transformer (#19567) chore(deps): bump peter-evans/find-comment from 1 to 2 (#19559) chore(data-warehouse): cleanup unused celery code and extend time (#19568) Revert "feat(data-warehouse): hubspot integration" (#19569) feat(data-warehouse): hubspot integration (#19529) feat: Feature gate session replay controls using available_product_features (#19401) fix: Padding on bullet lists (#19565) chore: Post 3000 LemonButtton cleanup (#19540) chore(deps): bump aws-actions/amazon-ecr-login from 1 to 2 (#19558) ...
Problem
Need to only allow new users to have access to these controls.
Changes
👉 Stay up-to-date with PostHog coding conventions for a smoother review.
How did you test this code?