-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
3
-
None
-
None
-
None
Description
With the addition of the GuidedTourFeature capability in the Console API, the Console frontend should respect this setting and conditionally render the Guided Tour feature.
This enables:
- Cluster admins to opt in/out of Guided Tours
- Console CI environments to disable Guided Tours to improve Cypress test stability
This story focuses on frontend behavior changes and test configuration updates.
Motivation
- Eliminate Guided Tour–related flakiness in Cypress tests
- Align Guided Tour behavior with Console capability model
- Improve admin control over Console UX features
Scope
- Gate Guided Tour rendering behind the GuidedTourFeature capability
- Ensure Guided Tour is not rendered when the capability is disabled
- Update Cypress test runs to explicitly disable the Guided Tour capability
Acceptance Criteria
- Vendor API changes into console repository
- Console frontend reads the GuidedTourFeature capability from the API
-
- Guided Tour is rendered only when the capability is enabled
-
- Guided Tour is not rendered or initialized when the capability is disabled
- Console Cypress tests run with GuidedTourFeature disabled
Note: https://github.com/openshift/console/pull/15841 which is already disabling the GuidedTour
- depends on
-
CONSOLE-4986 Add Guided Tour capability flag to Console API and vendor it into console-operator
-
- To Do
-