Owner: Architect:

Story (Required)

As an OpenShift user i would like to list helm releases as ususal.

Background (Required)

We are currently making use of `/api/helm/releases` endpoint to return helm releases to ui. The same api is used in topology too to create a map. In topology we show the manifests, release notes along with the other release information. We are not showing any such information on list releases page and hence returning the complete data to ui does not make sense.

Glossary

<List of new terms and definition used in this story>

Out of scope

<Defines what is not included in this story>

In Scope

<Defines what is included in this story>

Approach(Required)

We can add a flag called as isTopology bool flag to the network call and return the complete information if the call is made from topology else return limited information.

Demo requirements(Required)

Not Applicable

Dependencies

None

Edge Case

_<Describe edge cases to consider when implementing the story and defining
tests>_

Acceptance Criteria

Api should return response as before and the user experience remains the same.

Document is updated to reflect the change in request body.

Oc helm cli changes.

Development:

QE:
Documentation: Yes/No (needs-docs|upstream-docs / no-doc)

Upstream: <Inputs/Requirement details: Concept/Procedure>/ Not
Applicable

Downstream: <Inputs/Requirement details: Concept/Procedure>/ Not
Applicable

Release Notes Type: <New Feature/Enhancement/Known Issue/Bug
fix/Breaking change/Deprecated Functionality/Technology Preview>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

v

Legend

Unknown

Verified

Unsatisfied