Skip to content

Conversation

@its-mitesh-kumar
Copy link
Member

@its-mitesh-kumar its-mitesh-kumar commented Aug 26, 2025

Description

This PR updates all 77 marketplace plugin YAML files to use the new object structure for the support field, replacing the previous string format with a structured approach that includes both support provider name and support level.

Plugin sheet for Support Level and Provider for reference.

Issue

For issue https://issues.redhat.com/browse/RHIDP-8469

Changes Made

Schema Update

  • Updated the marketplace plugin schema to support both string (backward compatibility) and object formats
  • Added enum validation for support levels: ga, tech-preview, dev-preview
  • Schema now accepts both formats via oneOf pattern

Plugin Files Updated (77 total)

All plugin files in catalog-entities/marketplace/plugins/ converted from:

# Old format
support: tech-preview

To:

# New format  
support:
  name: Red Hat
  level: tech-preview

RHDH Marketplace Plugin Classification

Classification by Support.Name

Red Hat (66 plugins)

  1. 3scale
  2. adoption-insights
  3. analytics-provider-segment
  4. ansible-plugin
  5. argocd-scaffolder-actions
  6. azure-container-registry
  7. azure-devops
  8. azure-repositories
  9. backstage-community-plugin-quay
  10. bitbucket-cloud-catalog-integration
  11. bitbucket-cloud-scaffolder-actions
  12. bitbucket-server-catalog-integration
  13. bulk-import
  14. contrib-techdocs-addons
  15. datadog
  16. dynatrace-community
  17. extensions
  18. github-actions
  19. github-catalog-integration
  20. github-insights
  21. github-issues
  22. github-org-catalog-integration
  23. github-pull-requests
  24. github-scaffolder-actions
  25. gitlab-catalog-cards
  26. gitlab-scaffolder-actions
  27. global-floating-action-button
  28. global-header
  29. home-page
  30. http-request-scaffolder-action
  31. jenkins
  32. jfrog-artifactory
  33. jira
  34. keycloak-catalog-integration
  35. kubernetes
  36. kubernetes-backend
  37. kubernetes-scaffolder-actions
  38. ldap-catalog-integration
  39. lighthouse
  40. lightspeed
  41. microsoft-graph-catalog-integration
  42. nexus-repository-manager
  43. notifications
  44. notifications-email
  45. openshift-cluster-manager
  46. optimizations
  47. orchestrator
  48. orchestrator-scaffolder-actions
  49. pagerduty
  50. pingidentity
  51. quay-scaffolder-actions
  52. quickstart
  53. rbac
  54. redhat-argocd
  55. regex-scaffolder-actions
  56. roadie-argocd
  57. scaffolder-relation-processor-catalog-integration
  58. servicenow
  59. servicenow-scaffolder-actions
  60. signals
  61. signals-backend
  62. sonarqube-catalog-cards
  63. tech-radar
  64. techdocs
  65. tekton
  66. topology

Backstage Community (8 plugins)

  1. azure-scaffolder-actions
  2. bitbucket-server-scaffolder-actions
  3. gerrit-scaffolder-actions
  4. gitlab-catalog-integration
  5. gitlab-org-catalog-integration
  6. roadie-scaffolder-util-actions
  7. security-insights
  8. sonarqube-scaffolder-actions

Third-Party Vendors (2 plugins)

  1. IBM: ibm-apiconnect-backstage
  2. Dynatrace: dynatrace-commercial

Classification by Support.Level

GA (General Availability) (26 plugins)

  1. adoption-insights
  2. analytics-provider-segment
  3. ansible-plugin
  4. backstage-community-plugin-quay
  5. contrib-techdocs-addons
  6. dynatrace-commercial
  7. github-catalog-integration
  8. github-org-catalog-integration
  9. github-scaffolder-actions
  10. global-floating-action-button
  11. global-header
  12. home-page
  13. ibm-apiconnect-backstage
  14. keycloak-catalog-integration
  15. kubernetes-backend
  16. kubernetes-scaffolder-actions
  17. openshift-cluster-manager
  18. quay-scaffolder-actions
  19. quickstart
  20. rbac
  21. regex-scaffolder-actions
  22. roadie-argocd
  23. signals-backend
  24. techdocs
  25. tekton
  26. topology

Tech-Preview (48 plugins)

  1. 3scale
  2. argocd-scaffolder-actions
  3. azure-container-registry
  4. azure-devops
  5. azure-repositories
  6. azure-scaffolder-actions
  7. bitbucket-cloud-catalog-integration
  8. bitbucket-cloud-scaffolder-actions
  9. bitbucket-server-catalog-integration
  10. bitbucket-server-scaffolder-actions
  11. bulk-import
  12. datadog
  13. dynatrace-community
  14. extensions
  15. gerrit-scaffolder-actions
  16. github-actions
  17. github-insights
  18. github-issues
  19. github-pull-requests
  20. gitlab-catalog-cards
  21. gitlab-catalog-integration
  22. gitlab-org-catalog-integration
  23. gitlab-scaffolder-actions
  24. http-request-scaffolder-action
  25. jenkins
  26. jfrog-artifactory
  27. jira
  28. kubernetes
  29. ldap-catalog-integration
  30. lighthouse
  31. microsoft-graph-catalog-integration
  32. nexus-repository-manager
  33. notifications
  34. notifications-email
  35. optimizations
  36. orchestrator
  37. orchestrator-scaffolder-actions
  38. pagerduty
  39. pingidentity
  40. redhat-argocd
  41. roadie-scaffolder-util-actions
  42. scaffolder-relation-processor-catalog-integration
  43. security-insights
  44. servicenow-scaffolder-actions
  45. signals
  46. sonarqube-catalog-cards
  47. sonarqube-scaffolder-actions
  48. tech-radar

Dev-Preview (2 plugins)

  1. lightspeed
  2. servicenow

Summary Statistics

By Support Provider (support.name)

Support Provider Number of Plugins
Red Hat 66
Backstage Community 8
Third-Party Vendors 2
- IBM 1
- Dynatrace 1

By Support Level (support.level)

Support Level Number of Plugins
GA (General Availability) 26
Tech-Preview 48
Dev-Preview 2

Support Level Distribution by Provider

Provider GA Tech-Preview Dev-Preview Total
Red Hat 24 40 2 66
Backstage Community 0 8 0 8
Third-Party Vendors 2 0 0 2

Total Marketplace Plugins: 76

Related

@its-mitesh-kumar its-mitesh-kumar marked this pull request as draft August 26, 2025 05:14
@openshift-ci openshift-ci bot requested review from dzemanov and kadel August 26, 2025 05:14
@its-mitesh-kumar its-mitesh-kumar changed the title feat(marketplace): Convert support field to object structure with name and level properties feat(marketplace): convert support field to object structure with name and level properties Aug 26, 2025
@its-mitesh-kumar
Copy link
Member Author

/retest-required

1 similar comment
@its-mitesh-kumar
Copy link
Member Author

/retest-required

publisher: Red Hat
support: tech-preview
support:
name: Parfümerie Douglas
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the repo for the plugin is in the backstage community plugins, I think we should set this to "Backstage Community"

url: https://roadie.io/
support: tech-preview
support:
name: Roadie
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the repo for the plugin is in the backstage community plugins, I think we should set this to "Backstage Community"

author: Dynatrace
support: production
support:
name: Dynatrace
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing support.name from Dynatrace to Backstage Community.
FYI @benwilcock @christoph-jerolimov

url: https://roadie.io/
support: production
support:
name: Roadie
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing support.name from Roadie to Backstage Community.
FYI @benwilcock @christoph-jerolimov

publisher: Red Hat
support: tech-preview # production, tech-preview, dev-preveiw
support:
name: ImmobiliareLabs
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing support.name to Backstage Community here.
FYI @benwilcock @christoph-jerolimov

Signed-off-by: its-mitesh-kumar <[email protected]>
@its-mitesh-kumar
Copy link
Member Author

  • Ansible Plugin (yaml) → Is this the same as Ansible Automation Platform (AAP) listed in the sheet?

    • If yes, can I mark its support level as GA?
  • Azure Software Template Actions (azure-scaffolder-actions) → Couldn’t find it in the sheet.

    • Previously marked as support: tech-preview, so I’ll set it as level: tech-preview.
  • Red Hat Tech Preview (from sheet) → I am splitting it into structured format:

@github-actions
Copy link
Contributor

Signed-off-by: its-mitesh-kumar <[email protected]>
@github-actions
Copy link
Contributor

@invincibleJai
Copy link
Member

/retest

Copy link
Member

@christoph-jerolimov christoph-jerolimov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delay with the review.

I believe we

  1. should not use the provider "Backstage Community" when the level is "tech-preview". It's us or someone else, but currently its always on us.
  2. when the support level is community we could maybe also say "Backstage Community" and not us. This is just the case for servicenow. Since it is developed by us its also okay to say Red Hat. I will ping @benwilcock on slack for this.

author: Backstage Community
support: tech-preview
support:
provider: Backstage Community

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think when its Tech Preview we should say support is from Red Hat

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@christoph-jerolimov, I am waiting for final decision of this discussion for updating it.

author: Backstage Community
support: tech-preview
support:
provider: Backstage Community

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here, for tech preview support it should be Red Hat

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@christoph-jerolimov, I am waiting for final decision of this discussion for updating it.

publisher: Red Hat
lifecycle: active
support: tech-preview
# support: tech-preview

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please remove this old line

Suggested change
# support: tech-preview

support: tech-preview
support:
provider: Red Hat
level: generally-available

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

publisher: Red Hat
support: tech-preview
support:
provider: Backstage Community

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for tech-preview it should be Red Hat

publisher: Red Hat
support: tech-preview
support:
provider: Backstage Community

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for tech-preview it should be Red Hat

publisher: Red Hat
support: tech-preview
support:
provider: Backstage Community

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

when its tech-review it should be Red Hat

spec:
support: dev-preview
support:
provider: Red Hat

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
provider: Red Hat
provider: Backstage Community

When its not DP, TP @benwilcock , we don't say we support it, or?

@christoph-jerolimov
Copy link
Member

Fyi, we can't merge this PR yet because the extensions catalog will show no plugins with just this updated entities. We also need to update the extensions/marketplace wrapper.

(This must not be handled in this PR. But this must be merged before. For this we need to release it first on rhdh-plugins...)

/hold

@github-actions
Copy link
Contributor

github-actions bot commented Oct 1, 2025

@christoph-jerolimov
Copy link
Member

Marketplace PR #3479 was merged, this should finally unhold this PR as well. Please rebase this PR so that we can test both together. Thanks a lot @its-mitesh-kumar

/unhold

lifecycle: active
support: tech-preview
support:
provider: Red Hat
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

provider is RH but the authors are Backstage Community? so we SUPPORT it but don't OWN it?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this is correct :)

We support it as tech-preview because we bundle it with a wrapper, so we're responsible.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 1, 2025

@openshift-ci
Copy link

openshift-ci bot commented Oct 1, 2025

@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-tests a856b7f link true /test e2e-tests

Full PR test history. Your PR dashboard.

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.

@its-mitesh-kumar
Copy link
Member Author

/test e2e-ocp-helm

Copy link
Member

@christoph-jerolimov christoph-jerolimov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating this again and again. Thanks. This lgtm 👍

Verified on a cluster as well:

image

/lgtm
/approve

@openshift-ci
Copy link

openshift-ci bot commented Oct 1, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christoph-jerolimov

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

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [christoph-jerolimov]

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

@openshift-ci openshift-ci bot added the approved label Oct 1, 2025
@christoph-jerolimov
Copy link
Member

/retest

@openshift-merge-bot openshift-merge-bot bot merged commit acd1a3e into redhat-developer:main Oct 1, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants