docs: add warning on using non-uuid name for openssh nodes

[stevenGravy]

Using a non-uuid can result in the web ui showing this on access attempts

[github-actions]

Amplify deployment status

Branch	Commit	Job ID	Status	Preview	Updated (UTC)
stevenGravy/docs/nonuuidwarning	8c1a444	5	✅SUCCEED	stevengravy-docs-nonuuidwarning	2025-01-09 17:05:40

[rosstimothy]

If we fix the current error, then half of this warning seems moot. Can we instead make the wording in the section above more forceful about using a UUID?

[stevenGravy]

If we fix the current error, then half of this warning seems moot. Can we instead make the wording in the section above more forceful about using a UUID?

Please see update for the name.

[stevenGravy]

Thanks, applied

…

On Thu, Jan 9, 2025 at 10:58 AM rosstimothy ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In docs/pages/enroll-resources/server-access/openssh/openssh-manual-install.mdx <#50906 (comment)> : > +The `metadata.name` field isn't mandatory, but setting it here will save you some work later. Using +a non-UUID name can result in access errors when Teleport finds the node in its inventory. Again, I don't think we should be too specific with our warning, as we may very well be able to fix the current issue. I think we should instead put stronger encouragement to use a UUID if users plan to populate this field directl. ⬇️ Suggested change -The `metadata.name` field isn't mandatory, but setting it here will save you some work later. Using -a non-UUID name can result in access errors when Teleport finds the node in its inventory. +The `metadata.name` field isn't mandatory, but if supplied, it must be a universal unique identifier (UUID). To generate a new UUID suitable for a `node` name — Reply to this email directly, view it on GitHub <#50906 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOPERQJFKIYGAC37WF2TGWD2J2MCDAVCNFSM6AAAAABU4EDUJSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKNBQGMYTOMZQG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>