You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to #8823, the RotateAuth endpoint for the cluster server should accept the cluster name as a way of knowing token to rotate. At this point, all other endpoints for the cluster server accept both the server and name as ways of identifying a cluster. RotateAuth should be the same.
Motivation
For some users, it is simpler to identify clusters by a name rather than by the server url. It should also be a consistent experience for users interacting with the cluster server.
Proposal
This should be implemented in a way similar to #8823. Also, changing the CLI/UI to allow names should be considered as part of this change to allow users to easily consume this change.
Summary
Similar to #8823, the RotateAuth endpoint for the cluster server should accept the cluster name as a way of knowing token to rotate. At this point, all other endpoints for the cluster server accept both the server and name as ways of identifying a cluster. RotateAuth should be the same.
Motivation
For some users, it is simpler to identify clusters by a name rather than by the server url. It should also be a consistent experience for users interacting with the cluster server.
Proposal
This should be implemented in a way similar to #8823. Also, changing the CLI/UI to allow names should be considered as part of this change to allow users to easily consume this change.
The endpoint func in question is here.
For the CLI, the rotate auth command would need to be changed to also accept the name of the cluster instead of just the server.
The text was updated successfully, but these errors were encountered: