Closed jknipes closed 6 months ago
cc: @holdenhinkle
Hey team! Please add your planning poker estimate with Zenhub @BSmolensky @laucon
@BSmolensky & @laucon please add your planning poker estimates
Moved to top of Backlog for an upcoming sprint
@jknipes I contacted Holden on the Slack channel where he initiated the issue (link). My message (link): Hi Holden. I’m working on this issue (ZH ticket 77896). I created a draft of this page (source page) in my PC repo and made the following changes: Dev doc -> Infrastructure -> Feature toggles guide -> 2. Configure Flipper UI settings -> Percentage of Logged in Users -> 2nd Paragraph: “If the feature toggle’s actor_type in config/features.yml is set to cookie_id rather than user, the feature instead applies to only a percentage of users for the duration of a cookie within a single browser, regardless of their logged in status. Setting actor_type to cookie_id ONLY AFFECTS THE FRONTEND, NOT THE BACKEND. This is useful when you need to apply a staged rollout that involves an unauthenticated user experience.”
Are you okay with this language edit? If not, let’s discuss more options. Thank you, Holden. I look forward to talking with you soon!
@jknipes Holden approved 3 changes/updates:
Percentage of Users If the feature toggle's actor_type in config/features.yml is set to cookie_id rather than user, the feature instead applies to only a percentage of users for the duration of a cookie within a single browser, regardless of their logged in status. Setting actor_type to cookie_id ONLY AFFECTS THE FRONTEND, NOT THE BACKEND. This is useful when you need to apply a staged rollout that involves an unauthenticated user experience. Logged-in Users Enable the feature for only a percentage of logged-in users. It will be applied to the same users each time they return to the site (even when they log out and back in) as long as you don’t change the percentage. Not Logged-in Users If the feature toggle’s actor_type in config/features.yml is set to cookie_id rather than user, the feature instead applies to only a percentage of users for the duration of a cookie within a single browser, regardless of their logged in status. This is useful when you need to apply a staged rollout that involves an unauthenticated user experience.
Updates are migrated to the Developer docs source page.
Page has deployed successfully, moving to Done
Issue Description
This page on Platform Website needs to be updated to advise re: Setting
actor_type
tocookie_id
ONLY AFFECTS THE FRONTEND, NOT THE BACKENDSlack Support Thread: HERE
Tasks
Acceptance Criteria
[x] Confirm Developer docs Platform page appears correctly after deployment
How to configure this issue
product support
,analytics-insights
,operations
,service-design
,Console-Services
,tools-fe
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)bug
,request
,discovery
,documentation
, etc.)