Skip to content

[chore] Updating orchestrator npm packages to OCI artifacts#2231

Merged
openshift-merge-bot[bot] merged 9 commits intoredhat-developer:mainfrom
OpinionatedHeron:startOrchestrator
Feb 8, 2026
Merged

[chore] Updating orchestrator npm packages to OCI artifacts#2231
openshift-merge-bot[bot] merged 9 commits intoredhat-developer:mainfrom
OpinionatedHeron:startOrchestrator

Conversation

@OpinionatedHeron
Copy link
Copy Markdown
Member

Description

Updating orchestrator npm packages to the relevant OCI Artifacts to reflect updates to RHDH.

npm packages were causing the scaffolder plugin to throw an error during startup

Which issue(s) does this PR fix or relate to

RHDHBUGS-2527

PR acceptance criteria

  • Tests
  • Documentation

How to test changes / Special notes to the reviewer

Deploy Operator-based instance of RHDH with the orchestrator plugins enabled.

Signed-off-by: Leanne Ahern <lahern@redhat.com>
Comment thread config/profile/rhdh/default-config/dynamic-plugins.yaml Outdated
Comment thread config/profile/rhdh/default-config/dynamic-plugins.yaml Outdated
Comment thread config/profile/rhdh/default-config/dynamic-plugins.yaml Outdated
Comment thread config/profile/rhdh/default-config/dynamic-plugins.yaml Outdated
Comment thread config/profile/rhdh/default-config/dynamic-plugins.yaml Outdated
@rm3l
Copy link
Copy Markdown
Member

rm3l commented Jan 29, 2026

/cherry-pick release-1.9

@openshift-cherrypick-robot
Copy link
Copy Markdown

@rm3l: once the present PR merges, I will cherry-pick it on top of release-1.9 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-1.9

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.

Comment thread config/profile/rhdh/default-config/dynamic-plugins.yaml Outdated
Comment thread config/profile/rhdh/default-config/dynamic-plugins.yaml Outdated
Comment thread config/profile/rhdh/default-config/dynamic-plugins.yaml Outdated
Comment thread config/profile/rhdh/default-config/dynamic-plugins.yaml Outdated
Comment thread config/profile/rhdh/default-config/dynamic-plugins.yaml
@nickboldt
Copy link
Copy Markdown
Member

/cherry-pick release-1.9

If we use quay refs here instead, you can't cherry pick because the plugins will be using different tags (1.9.0-- or 1.10.0--) and therefore also different digests.

rm3l added 2 commits February 2, 2026 12:04
This option is supported as of RHDH 1.9 and allows inheriting
the version from the dynamic-plugins.default.yaml (coming from
the plugin catalog index image).
This way, we are sure to use the default plugin version.

NOTE: For this to work properly, the plugin refs should match.
So if the orchestrator plugins refs are changed later to quay.io
or registry.access.redhat.com in the DPDY, we should update them
here as well.
@rm3l
Copy link
Copy Markdown
Member

rm3l commented Feb 2, 2026

/cherry-pick release-1.9

If we use quay refs here instead, you can't cherry pick because the plugins will be using different tags (1.9.0-- or 1.10.0--) and therefore also different digests.

Yeah, this is exactly the kind of issues I think the {{inherit}} option will help solve: #2231 (comment)

Signed-off-by: Leanne Ahern <lahern@redhat.com>
Signed-off-by: Leanne Ahern <lahern@redhat.com>
Co-authored-by: OpinionatedHeron <OpinionatedHeron@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 3, 2026

⚠️ Files changed in bundle and installer generation!

Those changes to the operator bundle/installer manifests should have been pushed automatically to your PR branch.

NOTE: If the PR checks are stuck after this additional commit, manually close the PR and immediately reopen it to trigger the checks again.

@OpinionatedHeron OpinionatedHeron requested a review from rm3l February 3, 2026 16:22
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Feb 7, 2026

Copy link
Copy Markdown
Member

@rm3l rm3l left a comment

Choose a reason for hiding this comment

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

LGTM, but this should be documented as a breaking change in 1.9.0 for Operator users.

/lgtm

Comment thread docs/orchestrator.md
Comment on lines -83 to +92
- package: "@redhat/backstage-plugin-orchestrator@1.8.2"
disabled: false
- package: "@redhat/backstage-plugin-orchestrator-backend-dynamic@1.8.2"
disabled: false
dependencies:
- ref: sonataflow
- package: "@redhat/backstage-plugin-scaffolder-backend-module-orchestrator-dynamic@1.8.2"
disabled: false
- package: "@redhat/backstage-plugin-orchestrator-form-widgets@1.8.2"
disabled: false
- package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator:{{inherit}}'
disabled: false
- package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:{{inherit}}'
disabled: false
dependencies:
- ref: sonataflow
- package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:{{inherit}}'
disabled: false
- package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets:{{inherit}}'
disabled: false
Copy link
Copy Markdown
Member

@rm3l rm3l Feb 7, 2026

Choose a reason for hiding this comment

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

LGTM, but I think this would need to be documented as a known issue or breaking change in 1.9.0 (affecting only Operator users).
In 1.8, Operator users needed to explicitly use the @redhat/* NPM refs in their dynamic-plugins config in order to deploy the Orchestrator flavor, and now they would need to explicitly switch to the OCI refs, otherwise RHDH will fail to start IMO. So it will break Operator users that have existing Orchestrator-flavored instances of RHDH.

Copy link
Copy Markdown
Member

@rm3l rm3l Feb 8, 2026

Choose a reason for hiding this comment

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

I quickly tested an upgrade from 1.8 to this PR branch, and the init container failed to start until I manually update my dynamic-plugins config, which confirms this upgrade issue.

[...]

======= Skipping disabled dynamic plugin oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator@sha256:7355b244d463187b11174b091b10235167ffc6fbd9466ec3cff0a8b5b04d6e98!red-hat-developer-hub-backstage-plugin-orchestrator

======= Skipping disabled dynamic plugin oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator@sha256:6a138dd4c6bb7b98d7af58657395fc3ef3b96768276a2d65d9a7ef5fda52f2b5!red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator

======= Installing dynamic plugin @redhat/backstage-plugin-orchestrator@1.8.2
Traceback (most recent call last):
  File "/opt/app-root/src/install-dynamic-plugins.py", line 1284, in <module>
    main()
  File "/opt/app-root/src/install-dynamic-plugins.py", line 1269, in main
    _, plugin_config = install_plugin(plugin, plugin_path_by_hash, dynamic_plugins_root, skip_integrity_check)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/app-root/src/install-dynamic-plugins.py", line 917, in install_plugin
    plugin_path = installer.install(plugin, plugin_path_by_hash)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/app-root/src/install-dynamic-plugins.py", line 810, in install
    raise InstallException(f"No integrity hash provided for Package {package}")
InstallException: No integrity hash provided for Package @redhat/backstage-plugin-orchestrator@1.8.2

======= Cleaning up temporary catalog index directory
======= Removed lock file: /dynamic-plugins-root/install-dynamic-plugins.lock

@openshift-ci openshift-ci Bot added the lgtm label Feb 8, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Feb 8, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rm3l

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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 Feb 8, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 8228512 into redhat-developer:main Feb 8, 2026
9 checks passed
@openshift-cherrypick-robot
Copy link
Copy Markdown

@rm3l: #2231 failed to apply on top of branch "release-1.9":

Applying: Updating orchestrator npm packages to OCI artifacts
Using index info to reconstruct a base tree...
M	bundle/rhdh/manifests/backstage-operator.clusterserviceversion.yaml
M	bundle/rhdh/manifests/rhdh-default-config_v1_configmap.yaml
M	dist/rhdh/install.yaml
Falling back to patching base and 3-way merge...
Auto-merging dist/rhdh/install.yaml
Auto-merging bundle/rhdh/manifests/rhdh-default-config_v1_configmap.yaml
Auto-merging bundle/rhdh/manifests/backstage-operator.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in bundle/rhdh/manifests/backstage-operator.clusterserviceversion.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Updating orchestrator npm packages to OCI artifacts

Details

In response to this:

/cherry-pick release-1.9

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.

rm3l added a commit to rm3l/redhat-developer-hub-operator that referenced this pull request Feb 8, 2026
…eveloper#2231)

* Updating orchestrator npm packages to OCI artifacts

Signed-off-by: Leanne Ahern <lahern@redhat.com>

* Simplify the configuration by leveraging the {{inherit}} option

This option is supported as of RHDH 1.9 and allows inheriting
the version from the dynamic-plugins.default.yaml (coming from
the plugin catalog index image).
This way, we are sure to use the default plugin version.

NOTE: For this to work properly, the plugin refs should match.
So if the orchestrator plugins refs are changed later to quay.io
or registry.access.redhat.com in the DPDY, we should update them
here as well.

* Updating orchestrator packages from ghcr.io to quay.io

Signed-off-by: Leanne Ahern <lahern@redhat.com>

* Correcting quay.io path

Signed-off-by: Leanne Ahern <lahern@redhat.com>

* Regenerate bundle/installer manifests

Co-authored-by: OpinionatedHeron <OpinionatedHeron@users.noreply.github.com>

* Updating quay.io paths to use registry.access.redhat

Signed-off-by: Leanne Ahern <lahern@redhat.com>

---------

Signed-off-by: Leanne Ahern <lahern@redhat.com>
Co-authored-by: Armel Soro <asoro@redhat.com>
Co-authored-by: Gennady Azarenkov <gazarenkov@gmail.com>
Co-authored-by: Nick Boldt <nboldt@redhat.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: OpinionatedHeron <OpinionatedHeron@users.noreply.github.com>
openshift-merge-bot Bot pushed a commit that referenced this pull request Feb 8, 2026
…2282)

* Updating orchestrator npm packages to OCI artifacts



* Simplify the configuration by leveraging the {{inherit}} option

This option is supported as of RHDH 1.9 and allows inheriting
the version from the dynamic-plugins.default.yaml (coming from
the plugin catalog index image).
This way, we are sure to use the default plugin version.

NOTE: For this to work properly, the plugin refs should match.
So if the orchestrator plugins refs are changed later to quay.io
or registry.access.redhat.com in the DPDY, we should update them
here as well.

* Updating orchestrator packages from ghcr.io to quay.io



* Correcting quay.io path



* Regenerate bundle/installer manifests



* Updating quay.io paths to use registry.access.redhat



---------

Signed-off-by: Leanne Ahern <lahern@redhat.com>
Co-authored-by: Leanne Ahern <127859485+OpinionatedHeron@users.noreply.github.com>
Co-authored-by: Gennady Azarenkov <gazarenkov@gmail.com>
Co-authored-by: Nick Boldt <nboldt@redhat.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: OpinionatedHeron <OpinionatedHeron@users.noreply.github.com>
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.

5 participants