Epic Goal

The ability to use the API to download a search result in an easy to parse format such as CSV

Why is this important?

There is a lot of information inside RHACM that the customer is seeking to process in various ways

Scenarios

for example, a search for kind:ClusterServiceVersion (see screenshot as well)

Acceptance Criteria

The customer is able to download via the api the data in a format easy to parse by a spreadsheet program such as excel. The api documentation should provide an example

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>