-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add version incompatibility warning to Connect #51832
base: master
Are you sure you want to change the base?
Conversation
9ca0592
to
3fd1f1e
Compare
@ravicious, I added the UI: In the end I didn't use the tsh copy, it was too long. |
size="small" | ||
onClick={props.disableVersionCheck} | ||
> | ||
<Cog size="small" mr={1} /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted it to indicate that it's a config option :p
Also, handle TOO_OLD first to mirror lib/client/api.go.
as="a" | ||
href={buildDownloadUrl(props.platform)} | ||
target="_blank" | ||
<ActionButton |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gzdunek I've adjusted the buttons slightly so that they look the same way as primaryAction
/secondaryAction
from Alert. The cog icon was a nice touch, but with the new buttons there wasn't enough space for it.
I also removed the wildcards from the warning about the client being too old and updated the UIs to get rid of the -aa suffix when showing min version.

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Next time we can think of adding some kind of a prop to alert to control where the action buttons are shown, as we now at least have two places for that. Though maybe that's something we should consult with the design team.
@@ -119,6 +122,9 @@ export function ClusterLoginPresentation({ | |||
clearLoginAttempt={clearLoginAttempt} | |||
shouldPromptSsoStatus={shouldPromptSsoStatus} | |||
passwordlessLoginState={passwordlessLoginState} | |||
shouldSkipVersionCheck={shouldSkipVersionCheck} | |||
disableVersionCheck={disableVersionCheck} | |||
platform={platform} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a fair share of prop drilling, but this is because useClusterLogin
doesn't use a context and the login modal is written in the old style.
Amplify deployment status
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢
Closes #32555.
This PR refactors the version compatibility detection logic from tsh so that it can be reused in Connect. Then we use it to display a version compatibility warning in Connect when logging in to a cluster.
changelog: Added version compatibility warnings to Teleport Connect when logging in to a cluster