Description

As a user, I want to more easily find information about RHACS within the HCC search and products section.

Acceptance criteria

When the user searches for "RHACS" or related entries (for example: acs, advanced cluster security, etc)) in the HCC search bar, a result will be returned that will direct the user to https://console.redhat.com/openshift/acs/overview

When the user views the HCC product drop down or goes to the services page All services page (https://console.redhat.com/allservices). There is a section for "Operators"

When the user views the HCC product drop down or goes to the services page All services page (https://console.redhat.com/allservices), under "Operators" there is a entry for RHACS that links the user to: https://console.redhat.com/openshift/acs/overview

Areas Impacted

Search

Product drop-down

All services page (https://console.redhat.com/allservices)

Out of scope

Any changes to OCMUI app functionality.

Testing implications

Unsure what team, if any, is responsible for testing changes.

------------------------------------------------------------------------------------------------------------------------

Implementation notes

There are two ways to add items to HCC search/product page. The first is to use the FEC utility and front-end operator (outlined in OCMUI-3330):

1. Onboarding to the FEC utility (POC shared in F2F): https://github.com/RedHatInsights/uhc-portal/compare/master...florkbr:uhc-portal:hcc-fec-build-tool-poc?expand=1
2. Updating to use the new frontend operator features (self service): https://github.com/RedHatInsights/chrome-service-backend/blob/main/docs/feo-migration-guide.md

The second is to use the legacy method which would involve making a PR in the https://github.com/RedHatInsights/chrome-service-backend repo.

1. Adding search entries (legacy): https://github.com/RedHatInsights/chrome-service-backend/blob/main/docs/search-index.md#adding-entries-to-search-index
2. Adding allservices entries (legacy): https://github.com/RedHatInsights/chrome-service-backend/blob/main/docs/cloud-services-config.md#all-services-dropdown-and-page

The expectation is that, right now, the second (legacy) approach would be taken.

More information needed

There are content questions that need to be addressed before implementation including:

• What is the description for each entry?