Skip to content

fix(orchestrator): drop module from translationResources example - #2753

Closed
lokanandaprabhu wants to merge 3 commits into
redhat-developer:mainfrom
lokanandaprabhu:fix/orchestrator-translation-pluginroot
Closed

fix(orchestrator): drop module from translationResources example#2753
lokanandaprabhu wants to merge 3 commits into
redhat-developer:mainfrom
lokanandaprabhu:fix/orchestrator-translation-pluginroot

Conversation

@lokanandaprabhu

@lokanandaprabhu lokanandaprabhu commented Jul 10, 2026

Copy link
Copy Markdown
Member

Summary

  • Remove the explicit module from Orchestrator appConfigExamples in rhdh-bsp-orchestrator.yaml
  • RHDH defaults to PluginRoot when module is omitted, matching the fix in rhdh-plugins#3729

Context

The previous example used module: Alpha for translationResources, which can cause intermittent page load failures due to a module initialization race on the Alpha default export. Omitting module is the preferred RHDH convention (same pattern as scorecard and other plugins).

Test plan

  • Verify metadata YAML is valid
  • Confirm example config matches updated orchestrator plugin app-config.yaml

Align appConfigExamples with the orchestrator plugin fix that loads
dynamic translations from PluginRoot instead of Alpha.

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions github-actions Bot added mandatory-workspace PR affects a workspace with required plugins for releases workspace-update PR modifies files in an existing workspace labels Jul 10, 2026
RHDH defaults to PluginRoot when module is omitted, matching the
orchestrator plugin fix for the Alpha module initialization race.

Co-authored-by: Cursor <cursoragent@cursor.com>
@lokanandaprabhu lokanandaprabhu changed the title fix(orchestrator): use PluginRoot for translationResources example fix(orchestrator): drop module from translationResources example Jul 13, 2026

@karthikjeeyar karthikjeeyar left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/approve
/lgtm

@lokanandaprabhu

Copy link
Copy Markdown
Member Author

/publish

@github-actions

Copy link
Copy Markdown
Contributor

Publish workflow — build skipped (only metadata files changed).

Metadata Validation

❌ Found 5 validation error(s):

File Kind Message
rhdh-bsp-orchestrator-backend-mod-loki.yaml mismatch OCI tag mismatch: expected "bs_1.52.0__1.2.6" but got "bs_1.49.4__1.2.6"
rhdh-bsp-orchestrator-backend.yaml mismatch OCI tag mismatch: expected "bs_1.52.0__8.9.5" but got "bs_1.49.4__8.9.5"
rhdh-bsp-orchestrator-form-widgets.yaml mismatch OCI tag mismatch: expected "bs_1.52.0__1.10.8" but got "bs_1.49.4__1.10.8"
rhdh-bsp-orchestrator.yaml mismatch OCI tag mismatch: expected "bs_1.52.0__5.7.13" but got "bs_1.49.4__5.7.13"
rhdh-bsp-scaffolder-backend-mod-orchestrator.yaml mismatch OCI tag mismatch: expected "bs_1.52.0__1.5.4" but got "bs_1.49.4__1.5.4"

@openshift-ci openshift-ci Bot removed the lgtm label Jul 13, 2026
@openshift-ci openshift-ci Bot added the lgtm label Jul 13, 2026
@sonarqubecloud

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown
Contributor

The file versions.json could not be synced from branch main into this because your PR is from a fork.

You should update the versions.json file with the following content:

{
    "backstage": "1.52.0",
    "node": "24.14.0",
    "cli": "1.11.4",
    "cliPackage": "@red-hat-developer-hub/cli"
}

@lokanandaprabhu

Copy link
Copy Markdown
Member Author

Handled in PR - #3269

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm mandatory-workspace PR affects a workspace with required plugins for releases workspace-update PR modifies files in an existing workspace

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants