Uploaded image for project: 'OpenShift Console'
  1. OpenShift Console
  2. CONSOLE-4729 Enable and integrate the OLM v1 operator catalog in the UI
  3. CONSOLE-4861

Sync 'techPreview' server configuration to frontend feature flag service

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None
    • OCP Console - Sprint 280

      As a Console Developer, I want the backend's 'techPreview' server configuration value to be automatically populated in the frontend feature flag service, so that I can easily gate and label components as 'Tech Preview' based on the cluster's global configuration.

      🚀 Acceptance Criteria

      • The 'techPreview' status (e.g., true/false) from the backend server configuration is correctly passed to the frontend.
      • This 'techPreview' value is injected into the window.SERVER_FLAGS object (or equivalent mechanism) at console load time.
      • A new, clearly named feature flag (e.g., TECH_PREVIEW) is created and registered with the console's feature flag service (e.g., useFlag).
      • When the backend configuration for 'techPreview' is enabled, the useFlag('TECH_PREVIEW') hook (or equivalent) returns true.
      • When the backend configuration for 'techPreview' is disabled (or unset/null), the useFlag('TECH_PREVIEW') hook returns false.
      • This new flag does not interfere with the existing DEV_PREVIEW or other developer-centric flags.

              Unassigned Unassigned
              rh-ee-jonjacks Jon Jackson
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: