Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-3187

{company-name} and Community Technology Preview (TP) plugins and actions are disabled by default

Prepare for Y ReleasePrepare for Z ReleaseRemove QuarterXMLWordPrintable

    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • RHIDP-2144 - RHDH 1.3 Release (Feature)
    • Hide
      Before this update, some {company-name} and Community Technology Preview (TP) plugins and actions were enabled by default:

      .Technology Preview plugins
      * @backstage-community/plugin-catalog-backend-module-scaffolder-relation-processor (changing in RHIDP-3643)

      .Community Support plugins
      * @backstage/plugin-scaffolder-backend-module-azure
      * @backstage/plugin-scaffolder-backend-module-bitbucket-cloud
      * @backstage/plugin-scaffolder-backend-module-bitbucket-server
      * @backstage/plugin-scaffolder-backend-module-gerrit
      * @backstage/plugin-scaffolder-backend-module-github
      * @backstage/plugin-scaffolder-backend-module-gitlab
      * @roadiehq/scaffolder-backend-module-http-request
      * @roadiehq/scaffolder-backend-module-utils

      With this update, all plugins included under the link:https://access.redhat.com/support/offerings/techpreview[Technology Preview scope of support], whether from {company-name} or the community, are disabled by default.

      .Procedure
      * If your workload requires these plugins, enable them in your custom resource or configmap using `disabled: false`.

      //See https://github.com/redhat-developer/red-hat-developer-hub/blob/main/dynamic-plugins.default.yaml for examples.
      Show
      Before this update, some {company-name} and Community Technology Preview (TP) plugins and actions were enabled by default: .Technology Preview plugins * @backstage-community/plugin-catalog-backend-module-scaffolder-relation-processor (changing in RHIDP-3643 ) .Community Support plugins * @backstage/plugin-scaffolder-backend-module-azure * @backstage/plugin-scaffolder-backend-module-bitbucket-cloud * @backstage/plugin-scaffolder-backend-module-bitbucket-server * @backstage/plugin-scaffolder-backend-module-gerrit * @backstage/plugin-scaffolder-backend-module-github * @backstage/plugin-scaffolder-backend-module-gitlab * @roadiehq/scaffolder-backend-module-http-request * @roadiehq/scaffolder-backend-module-utils With this update, all plugins included under the link: https://access.redhat.com/support/offerings/techpreview [Technology Preview scope of support], whether from {company-name} or the community, are disabled by default. .Procedure * If your workload requires these plugins, enable them in your custom resource or configmap using `disabled: false`. //See https://github.com/redhat-developer/red-hat-developer-hub/blob/main/dynamic-plugins.default.yaml for examples.
    • Removed Functionality
    • Done

      Story

      As a user of RHDH, I want to all Tech Preview plugins and actions disabled by default so that I do not accidentally deploy functionality that's not suitable for production

      Background

      Reference: https://access.redhat.com/articles/6966848

      • "NOT intended to be used for production environments or to address production use cases"
      • Both terms apply to functionality or installations that are “opt-in”, fully configurable, and default to being disabled. Customers must explicitly enable any preview functionality.

      There are a number of unsupported scaffolder actions/plugins.

      Red Hat Tech Preview plugins

      • @backstage-community/plugin-catalog-backend-module-scaffolder-relation-processor (changing in RHIDP-3643 from @janus-idp/backstage-plugin-catalog-backend-module-scaffolder-relation-processor)

      Community Support plugins

      • @backstage/plugin-scaffolder-backend-module-azure
      • @backstage/plugin-scaffolder-backend-module-bitbucket-cloud
      • @backstage/plugin-scaffolder-backend-module-bitbucket-server
      • @backstage/plugin-scaffolder-backend-module-gerrit
      • @backstage/plugin-scaffolder-backend-module-github
      • @backstage/plugin-scaffolder-backend-module-gitlab
      • @roadiehq/scaffolder-backend-module-http-request
      • @roadiehq/scaffolder-backend-module-utils

      We should disable these by default so customers can knowingly opt-in to functionality that they know is not supported and therefore assume the risks.

      Dependencies and Blockers

      QE impacted work

      Documentation impacted work

      Acceptance Criteria

            nickboldt Nick Boldt
            ktsao@redhat.com Kim Tsao
            RHIDP - Core Platform
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: