update message on empty tsh ls results#28095
Conversation
github-actions
Bot
added
size/sm
tsh
| Not seeing nodes? Your user's roles may not have matching node labels. If trying Teleport for the first time, follow this guide: | ||
|
|
||
| https://goteleport.com/docs/getting-started/linux-server/#step-46-create-a-teleport-user-and-set-up-two-factor-authentication | ||
| https://goteleport.com/docs/server-access/getting-started |
There was a problem hiding this comment.
Should we add a redirect so anyone using an older version of tsh doesn't get sent to a nonexistent page?
There was a problem hiding this comment.
This redirects to the getting started now. Doesn't look like we can have different redirections. Thoughts @ptgott ?
There was a problem hiding this comment.
This URL currently redirects to https://goteleport.com/docs/get-started, where we moved the Linux Server guide. I don't think it's possible right now to configure redirects according to referrer.
We could see if we can configure a redirect from that specific URL (including the fragment) to the Server Access getting started guide, though I'm not sure how the docs engine will handle that. We could try it on the local docs dev server, though
There was a problem hiding this comment.
I tried. Didn't work
There was a problem hiding this comment.
So should we change the redirect to match?
There was a problem hiding this comment.
Would it be possible to include the relevant information within the tsh ls output rather than link to the docs? That way:
- We don't need to keep track of drift between the docs and
tsh - Users don't need to switch contexts and follow a getting started guide that may not apply to them (e.g., if there's a misconfiguration they need to talk to a Teleport admin at their org about, or they were never intended to access servers in the first place without, say, an Access Request)
There was a problem hiding this comment.
The two most likely reasons are that there are no nodes that match the listing (tsh ls, tsh ls env=test) or the user's roles do not allow them to see that listing. We could put that wording in. thoughts?
There was a problem hiding this comment.
@rosstimothy please see update. Ex
Node Name Address Labels
--------- ------- ------
Not seeing nodes? Either no nodes are available or your user's roles do not match the labels of at least one node.
Check with your Teleport cluster administrator that your user's roles should have nodes available.
codingllama
left a comment
codingllama
left a comment
There was a problem hiding this comment.
The missing principals no longer impacts whether users see nodes or not
I didn't know that, that's a nice change.
| Not seeing nodes? Your user's roles may not have matching node labels. If trying Teleport for the first time, follow this guide: | ||
|
|
||
| https://goteleport.com/docs/getting-started/linux-server/#step-46-create-a-teleport-user-and-set-up-two-factor-authentication | ||
| https://goteleport.com/docs/server-access/getting-started |
ptgott
left a comment
ptgott
left a comment
There was a problem hiding this comment.
Approved with a minor suggestion
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
public-teleport-github-review-bot
Bot
removed request for
jimbishopp,
r0mant and
zmb3
|
@stevenGravy See the table below for backport results.
|
4 participants
The missing principals no longer impacts whether users see nodes or not. The link given here no longer exists. Updated to point at the server guide.