Repository navigation
docs(tunnels): explain session reuse and history deletion - #29
Merged
Merged
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
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.
Document Delete history in the Console and the owner-only
DELETE /api/v1/tunnels/{id}/recordendpoint. Explain that Stop retains history and active tunnels must be stopped before deletion. Clarify that an active browser session can be reused when opening a tunnel.The new OpenAPI operation comes from the built gateway at app commit
52917b3d6401dfee7ba1a23fb412c61be053df5e. Existing API definitions are unchanged.Validation: CLI generation, navigation, content checks, Mintlify validation and broken links passed.