Skip to content

[web-console] Change private feldera-triage-plugins package injection approach#6313

Merged
Karakatiza666 merged 1 commit into
mainfrom
fix-cloud-js-build
May 27, 2026
Merged

[web-console] Change private feldera-triage-plugins package injection approach#6313
Karakatiza666 merged 1 commit into
mainfrom
fix-cloud-js-build

Conversation

@Karakatiza666

Copy link
Copy Markdown
Contributor

During the compilation of web-console as a part of the Enterprise build, the enterprise repo injected the closed-source triage plugin reference to the web-console build configuration.

Previously, a plain module name ('@cloud/support-bundle-triage') was injected as FELDERA_PLUGINS_MODULE, forcing the triage plugin be discoverable inside web-console NPM scope - within feldera/node_modules. This was achieved with symlinking which was not reliable - caused build failure citing a "circular dependency" - as the triage plugin also references some JS packages in the feldera submodule.

The fix is to inject an absolute filesystem path instead of a package name as FELDERA_PLUGINS_ENTRY, and map the triage plugin module name the web-console code imports to that file path.

When FELDERA_PLUGINS_ENTRY is unset (open-source builds), all new code paths are no-ops - a stub virtual module is emitted exactly as before.

This PR will be followed up by the PR to the enterprise repo.

… approach

Signed-off-by: Karakatiza666 <bulakh.96@gmail.com>
@Karakatiza666 Karakatiza666 requested a review from mihaibudiu May 25, 2026 12:02

@mythical-fred mythical-fred left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM. Clean swap from package-name + node_modules symlink to absolute-path + resolve.alias. OSS path stays a no-op stub when FELDERA_PLUGINS_ENTRY is unset; server.fs.allow widening is dev-only and properly gated. Env-var rename (FELDERA_PLUGINS_MODULEFELDERA_PLUGINS_ENTRY) is acknowledged in the PR description as a paired enterprise-repo follow-up — fine. No tests since this is build-infra for a closed-source consumer; verification happens via the enterprise build.

@mihaibudiu mihaibudiu left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I have no idea what's going on here

@Karakatiza666 Karakatiza666 added this pull request to the merge queue May 26, 2026
@gz gz removed this pull request from the merge queue due to a manual request May 26, 2026
@Karakatiza666 Karakatiza666 added this pull request to the merge queue May 26, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks May 27, 2026
@Karakatiza666 Karakatiza666 added this pull request to the merge queue May 27, 2026
Merged via the queue into main with commit 55e4e89 May 27, 2026
1 check passed
@Karakatiza666 Karakatiza666 deleted the fix-cloud-js-build branch May 27, 2026 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants