Simplify tunneled E2E setup - #1079
Open
j0sh wants to merge 5 commits into
Open
Conversation
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
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.
Summary
Known blocker
The E2E suite still requires public Cloudflare quick tunnels because the current catalyst-api requires callback_url and rejects private object-store destinations. The focused TODO documents the follow-up: optional VOD callbacks plus an empty-by-default exact host:port allowlist enforced during validation and dialing, followed by configuring in-a-box for its local MinIO and Task Runner endpoints.
Local validation
The complete Docker-backed E2E suite will run in CI because Docker and cloudflared are not installed on the development host.