fix(deploy): allow any HTTPS host on sql.demo.altinity.cloud's connec… - #576
Merged
Conversation
…t-src The demo release's connect-src was bounded to a fixed 4-origin allowlist (the chart default), so "Advanced — connect to another server" against any other ClickHouse host was silently blocked by CSP and surfaced as a bare "Failed to fetch" with no indication the request never left the browser. This shared instance is used ad hoc against arbitrary clusters, so its values-demo.yaml override now sets connectSrc to the "https:" scheme-source instead of inheriting the fixed list. The chart's own secure-by-default is unchanged for every other install. Closes-context: #575 (follow-up UX gap, filed separately) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KWApnNReVKwis3HdFfeUga
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…t-src
The demo release's connect-src was bounded to a fixed 4-origin allowlist (the chart default), so "Advanced — connect to another server" against any other ClickHouse host was silently blocked by CSP and surfaced as a bare "Failed to fetch" with no indication the request never left the browser. This shared instance is used ad hoc against arbitrary clusters, so its values-demo.yaml override now sets connectSrc to the "https:" scheme-source instead of inheriting the fixed list. The chart's own secure-by-default is unchanged for every other install.
Closes-context: #575 (follow-up UX gap, filed separately)
Claude-Session: https://claude.ai/code/session_01KWApnNReVKwis3HdFfeUga
What & why
Checklist
npm testpasses (the per-file coverage gate is non-negotiable)npm run buildsucceeds (single-filedist/sql.html)src/core/, network insrc/net/(injected fetch), DOM insrc/ui/CHANGELOG.md([Unreleased]) updated if behavior or the deployed surface changed