EPIC Goal

Enable platform engineers to configure which columns are displayed in the Software Catalog table through app-config.yaml, without requiring source code modifications.

What are we trying to solve here?

Currently, RHDH displays a fixed set of columns in the Catalog table, including a "Created At" column that is hardcoded. Platform engineers have no declarative way to:

1. Hide unwanted default columns (e.g., "Created At")
2. Show only a specific subset of columns
3. Add custom columns based on entity metadata/annotations
4. Configure kind-specific columns (e.g., show different columns for Components vs APIs)
5. This forces users to modify source code or create custom plugins just to adjust table columns, which contradicts RHDH's goal of being a configurable platform.

Background/Feature Origin

Why is this important?

User Scenarios

Dependencies (internal and external)

Acceptance Criteria

[ ] Platform engineers can configure catalog.table.columns in app-config.yaml
[ ] exclude option hides specified default columns
[ ] include option shows only specified columns (takes precedence over exclude)
[ ] custom option adds new columns based on entity field paths
[ ] Custom columns support:

• [ ] title - Column header text
• [ ] field - Entity field path (dot notation and bracket notation for annotations)
• [ ] width - Optional column width
• [ ] sortable - Optional sorting capability (default: true)
• [ ] defaultValue - Value when field is missing
• [ ] kind - Optional kind filter for kind-specific columns

[ ] Default behavior (no configuration) maintains backward compatibility
[ ] Configuration schema is defined in config.d.ts with proper visibility tags
[ ] Unit tests cover all column customization scenarios
[ ] E2E tests validate column visibility in the UI

Release Enablement/Demo - Provide necessary release enablement details
and documents

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 Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>