Skip to content
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

Introduce a third (Enterprise) FF Cloud Tier #2653

Closed
3 tasks done
Tracked by #2329
MarianRaphael opened this issue Aug 26, 2023 · 2 comments
Closed
3 tasks done
Tracked by #2329

Introduce a third (Enterprise) FF Cloud Tier #2653

MarianRaphael opened this issue Aug 26, 2023 · 2 comments
Assignees
Labels
priority:high High Priority size:M - 3 Sizing estimation point
Milestone

Comments

@MarianRaphael
Copy link
Contributor

MarianRaphael commented Aug 26, 2023

Configuration of a third Enterprise tier (analogous to "Teams") with two exclusive features:

  • SSO (currently configurable via Admin, so no User-Teams interaction possible)
  • HA

Tasks

@MarianRaphael MarianRaphael added size:XXL - 13 Sizing estimation point size:XL - 8 Sizing estimation point and removed size:XXL - 13 Sizing estimation point labels Aug 26, 2023
@MarianRaphael MarianRaphael added this to the 1.12 milestone Aug 28, 2023
@MarianRaphael MarianRaphael added priority:high High Priority size:M - 3 Sizing estimation point and removed size:XL - 8 Sizing estimation point labels Aug 31, 2023
@knolleary knolleary self-assigned this Sep 1, 2023
@knolleary
Copy link
Member

We need to decide how to handle any existing 'Teams' teams that have turned on HA already.

If we turn off HA in the Teams tier and make it Enterprise only, that will leave those users stuck.

Options:

  1. If the HA feature flag is disabled for a TeamType, but we find an instance with it enabled, allow the user to disable HA on that instance, but do not allow them to enable.
  2. Find a way to administratively override feature flags for individual teams

Option 1 is probably the cleanest approach to take.


As for SSO - given there is no configuration within the Team regarding SSO, this is purely for us as admins to control who gets the feature enabled.

@MarianRaphael
Copy link
Contributor Author

Only one team (besides the FF Team) is affected. If this team is currently not in the "Teams" tier, we could maintain the migration path we used for the last migration. Otherwise, I would go with option 1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:high High Priority size:M - 3 Sizing estimation point
Projects
Archived in project
Archived in project
Development

No branches or pull requests

2 participants