This story is how to integrate OCM UI's Unleashed Feature Flags:

Production: https://ocm.unleash.devshift.net
Staging: https://ocm-stage.unleash.devshift.net

...with the HCC Preview mode, which is based on Unleashed Feature Flags located at:

Production: https://insights.unleash.devshift.net/
Staging: https://insights-stage.unleash.devshift.net/

Once we figure out which unleashed instance OCM UI should use, we can determine which feature flags should be available in Preview mode:

From Switch to new preview document:

Conditional preview feature flags
The unleash feature flags were extended with the “platform.chrome.ui.preview” context field. That context field is available today, in all environments. Use it to enable/disable features for stage or production environments only.

Provided example is using stage, but works exactly the same in production unleash

1. Go to https://insights-stage.unleash.devshift.net/ (https://insights.unleash.devshift.net/ for prod)
2. (Optional) create a new feature toggle
3. Open a feature toggle
4. Add or update rollout strategy
5. Go to the strategy targeting tab
6. Click on “Add constraint”
7. In the “Context Field” dropdown, select “platform.chrome.ui.preview" context field
8. In the “Operator” dropdown select the “IN” value
9. In the “Values” text field, type “true” or select “true” checkbox

OCM UI typically enables a feature flag in staging, and disables it in production so it is not visible to customers.  If we want a feature to be available in Preview mode on production, should we enable the feature flag in production, but give it a `platform.chrome.ui.preview` constraint?

OCM UI's candidate branch is currerntly being deployed to console.redhat.com/preview/openshift, and since that is going away, should we be looking at using console.stage.redhat.com?  Is that where insights-stage unleashed flags are being used?

cc mhajtol ?

From Martin Hajtol <mhajtol@redhat.com>
Mon, Jun 10, 12:02 PM

WHAT & WHEN

In June of 2024 we’ll start to support the new “merge preview”, while still maintaining the old way. We will then plan on ending the “old” way of preview (aka having console.redhat.com/preview) as its own URL and only support using feature flags to mark items as preview. On August 1, 2024 we will end the URL version of preview, and only have the new way available.

WHO

This will require changes from the following: all services that utilize console.redhat.com/preview/

This change impacts only the frontend portion of HCC. Backend services are not affected.

HOW

See required and recommended code changes in this document: Switch to new preview.

ADDITIONAL INFORMATION

Please review the following post for details of the change, requirements, background information, and references:

ADR-044: Migrate the UI preview env out of the /preview URL to a feature flag environment

ADR-045: Shared Feature Toggle Strategy for HCC

Hybrid Cloud Console - Preview mode design doc

Relevant Jira(s): https://issues.redhat.com/browse/RHCLOUD-31984

ConsoleDot Actions Required & Releases Source page is here.

We believe this change will require small or no effort at all in most cases, that's why the timeline is a bit aggressive. But as always, if you are not able to perform these changes on time, please speak up. You can contact us by replying to this email or on slack #forum-consoledot-ui.

Acceptance Criteria