feat(catalog): add catalog table column customization via app-config

[its-mitesh-kumar]

Description

This PR introduces the ability for platform engineers to customize which columns are displayed in the Software Catalog table via app-config.yaml configuration.

Key changes:

• Add catalog.table.columns configuration schema with include, exclude, and custom options
• Create column factory (createCatalogColumnsFunc) to build columns from configuration
• Pass configuration through DynamicRootContext to AppBase
• Replace hardcoded columns in AppBase with configuration-driven approach

UI after changes

Screen.Recording.2026-01-27.at.3.mp4

Fixes:

• Fixed https://issues.redhat.com/browse/RHIDP-11577
• Fixed https://issues.redhat.com/browse/RHIDP-11578
• Fixed https://issues.redhat.com/browse/RHIDP-11579

Configuration Examples

Hide specific columns:

catalog:
  table:
    columns:
      exclude:
        - createdAt

Show only specific columns:

catalog:
  table:
    columns:
      include:
        - name
        - owner
        - type

Add custom metadata columns:

catalog:
  table:
    columns:
      custom:
        - title: "Security Tier"
          field: "metadata.annotations['custom/security-tier']"
          width: 120
          sortable: true
          defaultValue: "Not Set"
        - title: "Cost Center"
          field: "metadata.labels['cost-center']"
          sortable: true

Show a column only for specific entity kinds:

catalog:
  table:
    columns:
      custom:
        - title: "API Version"
          field: "spec.definition.version"
          kind: API
        - title: "Team"
          field: "spec.team"
          kind:
            - Component
            - Resource

PR acceptance criteria

Please make sure that the following steps are complete:

• GitHub Actions are completed and successful
• Unit Tests are updated and passing
• E2E Tests are updated and passing
• Documentation is updated if necessary (requirement for new features)
• Add a screenshot if the change is UX/UI related

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign zaperex for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-4068
• quay.io/rhdh-community/rhdh:pr-4068-1f5a5d2d

[sonarqubecloud]

Quality Gate passed

Issues
6 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-4068
• quay.io/rhdh-community/rhdh:pr-4068-58cde613

[openshift-ci]

@its-mitesh-kumar: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-ocp-helm	58cde61	link	true	/test e2e-ocp-helm

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[christoph-jerolimov]

/cc @christoph-jerolimov @ShiranHi @benwilcock @christophe-f

[christoph-jerolimov]

This is super interesting and a nice solution. Thanks a lot for that investigation and experiment. 👍

We need to check this with others, esp. PM. Until we have clear commitment I like to add the hold label to make clear that we need to discuss this first.

/hold