Type: Epic
Resolution: Done
Priority: Major
Fix Version/s: 1.6.0
Affects Version/s: None
Component/s: Marketplace
Labels:
- demo
- rhdh-1.6-candidate

Epic Name:
Export marketplace data to CSV for catalog.redhat.com
Size:
S
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Epic Status:
Done
Feature Link:
RHIDP-4547 - ETL Processing Of Plugin Metadata - For RHDH Extensions, Red Hat Catalog, And RHDH Docs Use Cases
Planning:

QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done
Intelligence Requested:
Market:

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

EPIC Goal

Create a tool to export marketplace plugin metadata to CSV format for product management consumption in Google Sheets

Background/Feature Origin

The Developer Hub marketplace stores plugin metadata in YAML format (kind: package and kind: plugin)
Product management needs this data in spreadsheet format for the plugins at catalog.redhat.com
We might extend the tool to update the yaml plugin metadata files from a CSV file

Why is this important?

Reduces manual effort in maintaining plugin metadata documentation
Ensures consistency between marketplace data, product management and catalog.redhat.com

User Scenarios

As a product manager, I want to view all marketplace plugin metadata in a spreadsheet

Acceptance Criteria

Script can read both package YAML and plugin YAML files
Script combines relevant metadata fields into a single CSV output
The latest version of the package is used for the plugin metadata
CSV format is compatible with Google Sheets import
The script can be part of https://github.com/redhat-developer/rhdh-plugins/tree/main/workspaces/marketplace but doesnt has to be packaged

depends on

RHIDP-6153 Review & Validate The Metadata For Extensions Marketplace Plugins

Closed

Ben Wilcock added a comment - 2025/02/28 9:39 AM - edited

cjerolim take a look at this spreadsheet where col A contains a list of the data items that get exposed in the web catalog. Cols E & F are a rough guide to where these may come from. The work to finalise the data mapping will need completing as part of this feature. We have another epic that may help with filling any gaps in the data: https://issues.redhat.com/browse/RHIDP-6153

Ben Wilcock added a comment - 2025/02/28 9:39 AM - edited cjerolim take a look at this spreadsheet where col A contains a list of the data items that get exposed in the web catalog. Cols E & F are a rough guide to where these may come from. The work to finalise the data mapping will need completing as part of this feature. We have another epic that may help with filling any gaps in the data: https://issues.redhat.com/browse/RHIDP-6153

Assignee:: Jackson Lee

Reporter:: Ben Wilcock

Team:: RHIDP - Frontend Plugins & UI

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2025/02/20 10:12 AM

Updated:: 2025/04/16 1:53 PM

Resolved:: 2025/03/25 2:22 PM

Details

Description

EPIC Goal

Background/Feature Origin

Why is this important?

User Scenarios

Acceptance Criteria

Attachments

Issue Links

Easy Agile Planning Poker

Activity

[RHIDP-6096] Export marketplace data to CSV for catalog.redhat.com

Collapse comment: Ben Wilcock added a comment - 2025/02/28 9:39 AM, Edited by Ben Wilcock - 2025/02/28 9:39 AM

Expand comment: Ben Wilcock added a comment - 2025/02/28 9:39 AM, Edited by Ben Wilcock - 2025/02/28 9:39 AM

People

Dates