Skip to content

Don't wait for Boundary tunnel teardown on quit - #2271

Merged
rolandwalker merged 1 commit into
mainfrom
RW/boundary-immediate-exit
Sep 25, 2026
Merged

rolandwalker merged 1 commit into
mainfrom
RW/boundary-immediate-exit

Conversation

@rolandwalker

Copy link
Copy Markdown
Contributor

Description

At /quit, mycli was waiting up to a couple of seconds to tear down the Boundary connection, and the logic allowed for an even longer wait.

Instead we should just exit, and let the terminated Boundary process take care of itself.

Other tunnel mechanisms (SSH and kubectl) are left untouched, since their teardown is faster in practice.

Checklist

  • I added this contribution to the changelog.md file.
  • I added my name to the AUTHORS file (or it's already there).
  • To lint and format the code, I ran
    uv run ruff check && uv run ruff format && uv run mypy --install-types .

At /quit, mycli was waiting up to a couple of seconds to tear down the
Boundary connection, and the logic allowed for an even longer wait.

Instead we should just exit, and let the terminated Boundary process
take care of itself.

Other tunnel mechanisms (SSH and kubectl) are left untouched, since
their teardown is faster in practice.
@rolandwalker rolandwalker self-assigned this Sep 25, 2026
@rolandwalker
rolandwalker merged commit 7f45c5a into main Sep 25, 2026
12 checks passed
@rolandwalker
rolandwalker deleted the RW/boundary-immediate-exit branch September 25, 2026 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant