Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[teleport-update] Improve clarity of error logs and address UX edge cases #52777

Merged
merged 11 commits into from
Mar 12, 2025

Conversation

sclevine
Copy link
Member

@sclevine sclevine commented Mar 4, 2025

This PR makes adds a few minor usability tweaks to teleport-update:

  • teleport-update status has more clear output when Teleport is not installed
  • teleport-update uninstall no longer requires the --force flag when run with a non-conflicting suffix
  • Running commands as a non-root effective user fails with a clear error
  • Logs after prefixed installations complete suggest commands that use the correct service name
  • Jitter can be terminated with SIGINT / SIGTERM

changelog: Improve clarity of error logs and address UX edge cases in teleport-update


The teleport-update binary will be used to enable, disable, and trigger automatic Teleport agent updates. The new auto-updates system manages a local installation of the cluster-specified version of Teleport stored in /opt/teleport.

RFD: #47126
Goal (internal): https://github.com/gravitational/cloud/issues/11856

@sclevine
Copy link
Member Author

sclevine commented Mar 4, 2025

(moving to draft to look into a more comprehensive fix for the --force flag change)

@sclevine sclevine marked this pull request as draft March 4, 2025 23:18
@sclevine sclevine changed the title [teleport-update] Usability improvements (low impact) [teleport-update] Improve clarity of logs and UX Mar 11, 2025
@sclevine sclevine changed the title [teleport-update] Improve clarity of logs and UX [teleport-update] Improve clarity of error logs and address UX edge cases Mar 11, 2025
@sclevine sclevine requested review from vapopov and hugoShaka March 11, 2025 06:01
@sclevine sclevine marked this pull request as ready for review March 11, 2025 06:01
@sclevine
Copy link
Member Author

Ready for review

@github-actions github-actions bot requested review from avatus and camscale March 11, 2025 06:02
@sclevine sclevine requested a review from hugoShaka March 12, 2025 16:49
@public-teleport-github-review-bot public-teleport-github-review-bot bot removed the request for review from avatus March 12, 2025 17:09
@sclevine sclevine enabled auto-merge March 12, 2025 17:56
@sclevine sclevine added this pull request to the merge queue Mar 12, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to a conflict with the base branch Mar 12, 2025
@sclevine sclevine force-pushed the sclevine/autoupdates-feedback branch from fc35ca5 to 48065ee Compare March 12, 2025 18:33
@sclevine sclevine enabled auto-merge March 12, 2025 18:34
@sclevine sclevine added this pull request to the merge queue Mar 12, 2025
Merged via the queue into master with commit 50dad3e Mar 12, 2025
41 checks passed
@sclevine sclevine deleted the sclevine/autoupdates-feedback branch March 12, 2025 19:13
@public-teleport-github-review-bot

@sclevine See the table below for backport results.

Branch Result
branch/v17 Failed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants