## Summary This rolls out `vue3_migrate_seat_management`, which switches 24 page entrypoints owned by group::seat management from the Vue 2 bundle to the Vue 3 bundle. There is no user-visible feature here: the UI is identical either way, and the flag only selects which JavaScript chunk Rails serves for the current user. We are doing this now because the repo-wide final sweep (gitlab-org/gitlab!261154) will move any page without its own migration MR onto the shared `vue3_migrate_final_sweep` flag in mid-19.6, and owning our own flag means seat management controls its own rollout and rollback instead of sharing one lever with roughly 234 other pages. - DRI: @lwanko - Team Slack channel: `#g_fulfillment_seat_management` ## What could go wrong? The affected pages are mostly admin and group administration surfaces (custom roles, service accounts, admin users, credentials and tokens, SSH keys, role promotion requests, GitLab Duo seat utilization, LDAP and SAML group links, the security credentials inventory, and usage quotas pending members), so the audience is largely group owners and instance admins. The exception is the user terms acceptance page, which any user can hit. Because only the bundle changes, a regression shows up as a page that fails to render or a broken interaction, not as incorrect or lost data. There is no schema change and no data migration, so rollback is a flag flip that serves the Vue 2 chunk again. Highest-risk pages by number of reachable Vue components: - User terms acceptance (108 components), and the only page in this set that every user can reach - Admin impersonation tokens (53 components) - Admin users list (34 components) ## Events <!-- Replace feature flag name in the link--> - [Exceptions with vue3_migrate_seat_management:1](https://log.gprd.gitlab.net/app/discover#/?_g=(time:(from:now-1d,to:now))&_a=(index:'7092c4e2-4eb5-46f2-8305-a7da2edad090',query:(language:kuery,query:'json.exception.feature_flag_states.keyword:%22vue3_migrate_seat_management:1%22'),columns:!(json.exception.class,json.exception.message,json.extra.workflow_id,json.meta.caller_id),sort:!(!(json.time,desc)))) - [Events with vue3_migrate_seat_management:1](https://log.gprd.gitlab.net/app/discover#/?_g=(time:(from:now-1d,to:now))&_a=(index:'7092c4e2-4eb5-46f2-8305-a7da2edad090',query:(language:kuery,query:'json.feature_flag_states:%22vue3_migrate_seat_management:1%22'),columns:!(json.meta.caller_id,json.feature_flag_states),sort:!(!(json.time,desc)))) - [Error rate and other graphs by modifying the examples in the Visualization Library](https://log.gprd.gitlab.net/app/visualize#/?_g=h@358d019&s=FF%20Observability) Feature Flag events are only logged by default for feature flags marked for the current or future milestones. To enable while the feature flag is active, see https://docs.gitlab.com/development/feature_flags/#logging ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#g_fulfillment_seat_management`. Background: [incremental rollout process](https://docs.gitlab.com/development/feature_flags/controls/#process), [feature actors](https://docs.gitlab.com/development/feature_flags/#feature-actors). **Non-production** ``` /chatops gitlab run feature set vue3_migrate_seat_management 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set vue3_migrate_seat_management true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set vue3_migrate_seat_management <percentage> --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss vue3_migrate_seat_management true /chatops gitlab run feature set --group=gitlab-org,gitlab-com vue3_migrate_seat_management true /chatops gitlab run feature set --user=lwanko vue3_migrate_seat_management true ``` ## Before global rollout Confirm the relevant gotchas before going to 100% — see [enabling a feature for GitLab.com](https://docs.gitlab.com/development/feature_flags/controls/#enabling-a-feature-for-gitlabcom): - [Docs + version history](https://docs.gitlab.com/development/documentation/feature_flags/) updated - [Breaking changes](https://docs.gitlab.com/development/documentation/release_notes/#deprecations-removals-and-breaking-changes) announced, if any - [Change management issue](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#feature-flags-and-the-change-management-process) opened, if required - [External API consumers](https://docs.gitlab.com/development/feature_flags/#do-not-use-feature-flags-in-external-api-consumers) handled with a fail-open mechanism, if applicable ## Cleanup Remove the flag once [deemed stable](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) — see [cleaning up](https://docs.gitlab.com/development/feature_flags/controls/#cleaning-up). Track it here, or open a follow-up [Feature Flag Cleanup issue](https://gitlab.com/gitlab-org/gitlab/-/work_items/new?description_template=Feature%20Flag%20Cleanup). Remove the flag and its YAML definition from the codebase, then: ``` /chatops gitlab run release check <merge-request-url> <milestone> /chatops gitlab run feature delete vue3_migrate_seat_management --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set vue3_migrate_seat_management false # production /chatops gitlab run feature set vue3_migrate_seat_management false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete vue3_migrate_seat_management --dev --pre --staging --staging-ref --production # remove entirely ```