## Summary Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/issues/607821) currently behind the `vue3_migrate_value_stream_analytics` feature flag. - DRI: @blabuschagne - Team Slack channel: `#g_optimize` > [!note] > Process and guidance live in the docs; this issue is just the commands and a place to track the rollout. > "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability. It is not the same as releasing the feature, which happens when the flag is removed. > [Feature flag controls](https://docs.gitlab.com/development/feature_flags/controls/) · [Feature flag lifecycle](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) ## What could go wrong? The flag switches the value stream analytics pages from the Vue 2 bundle to the Vue 3 (`@vue/compat`) bundle: project VSA (`Projects::CycleAnalyticsController#show`, which serves both the CE and EE experiences via the `ee_else_ce` bundle), group VSA (`Groups::Analytics::CycleAnalyticsController#show`), and the value stream create and edit forms at group and project level (`Groups::Analytics::CycleAnalytics::ValueStreamsController#new`/`#edit`, `Projects::Analytics::CycleAnalytics::ValueStreamsController#new`/`#edit`). If a page fails to render or the forms misbehave under Vue 3, disable the flag to revert to the Vue 2 bundle. The flag only changes which frontend bundle renders; the create and edit forms still write value stream configuration through the existing APIs, so a broken form blocks value stream management until the flag is disabled. Questions: `#vue3_migration`. ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#g_optimize`. 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_value_stream_analytics 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set vue3_migrate_value_stream_analytics true --dev --pre --staging --staging-ref ``` **Production**: percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set vue3_migrate_value_stream_analytics 25 --actors /chatops gitlab run feature set vue3_migrate_value_stream_analytics 50 --actors /chatops gitlab run feature set vue3_migrate_value_stream_analytics 100 --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --user=blabuschagne vue3_migrate_value_stream_analytics 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)). When removing the flag, also flip each of these six `vue3_migration.yml` files to `status: migrated` and drop their `feature_flag` line: - `app/assets/javascripts/pages/projects/cycle_analytics/show/vue3_migration.yml` - `ee/app/assets/javascripts/pages/groups/analytics/cycle_analytics/show/vue3_migration.yml` - `ee/app/assets/javascripts/pages/groups/analytics/cycle_analytics/value_streams/new/vue3_migration.yml` - `ee/app/assets/javascripts/pages/groups/analytics/cycle_analytics/value_streams/edit/vue3_migration.yml` - `ee/app/assets/javascripts/pages/projects/analytics/cycle_analytics/value_streams/new/vue3_migration.yml` - `ee/app/assets/javascripts/pages/projects/analytics/cycle_analytics/value_streams/edit/vue3_migration.yml` Track it here, or open a follow-up [Feature Flag Cleanup issue](https://gitlab.com/gitlab-org/gitlab/-/issues/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_value_stream_analytics --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set vue3_migrate_value_stream_analytics false # production /chatops gitlab run feature set vue3_migrate_value_stream_analytics false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete vue3_migrate_value_stream_analytics --dev --pre --staging --staging-ref --production # remove entirely ```