mengw15 opened a new pull request, #8623: URL: https://github.com/apache/texera/pull/8623
### What changes were proposed in this PR? Backport of #8562 to `release/v1.3`: a clean cherry-pick of its squash commit, no adaptations — five added lines across the single-node compose file, the dev compose file and the Helm chart's `extraEnv`. This branch needs it because #8550 already made RustFS the default object store here. RustFS sends no CORS headers unless `RUSTFS_CORS_ALLOWED_ORIGINS` is set (its reflective default was removed as CVE-2026-46685), while MinIO sent them by default — so without this change a v1.3 deployment renders no dataset file preview: the browser's cross-origin fetch of the presigned URL is blocked and the preview stays in its loading state. Opened manually by the v1.3 release manager: the automated fast path cherry-picked this cleanly and then pushed it straight to `release/v1.3`, where the Merge Queue ruleset rejected the push (`GH013`, [run 35305278774](https://github.com/apache/texera/actions/runs/35305278774)). The Actions-app bypass meant to unblock that path (#8379) was never created — asfyaml rejects an `Integration` bypass actor — and the failing job's notification 403s for want of `pull-requests: write`, so the loss left neither a backport PR nor a comment on #8562. The `release/v1.2` backport did get a PR (#8585, merged) only because it took the other code path. See #8377. Source: af6e0fdd96f44c1d575278b9fd12ed61ce6a8640 ### Any related issues, documentation, discussions? Backport of #8562. Originally linked #8557. ### How was this PR tested? The change is identical to #8562 (configuration only, no application code); the backport tree is verified byte-identical to cherry-picking the squash commit onto `release/v1.3`. Release-branch CI runs the full matrix on this PR, including the integration jobs that provision RustFS. ### Was this PR authored or co-authored using generative AI tooling? Yes. Generated-by: Claude Code (claude-opus-5) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
