Repository navigation
Conversation
This branch has not been deployed
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.
Keep named-tunnel publisher credentials on the runtime origin while interactive CLI requests retain Gateway and their user-session lifecycle. Recognise known production/staging HTTPS aliases and standard ports; explicit custom authorities remain configured. Explicit Authorization overrides are case-insensitive and never borrow, refresh or erase the saved human session. Credential requests and refreshes reject redirects.
Validation:full210-test CLI suite passed, including publisher/user separation, rejected machine credentials, lowercase header overrides, custom authorities and redirect recovery.
Stacked on#76 to preserve its independent review. DRAFT / rollout dependency: hold merge and CLI release until dataplicity-prelude#3513 supplies runtime ingress and the combined staging backend/router passes real published Prelude and supported legacy-agent qualification. No release tag or production rollout is dispatched.