meshery/meshery

[mesheryctl] UX: Need more informative inactive token message

Open

#4,604 opened on Nov 11, 2021

View on GitHub
 (22 comments) (0 reactions) (0 assignees)HTML (10,013 stars) (3,101 forks)batch import
area/uxcomponent/mesheryctlhelp wantedissue/remindissue/willfixkind/enhancementlanguage/go

Description

See mesheryctl Command Tracker for current status of commands.

Current Behavior

Users of mesheryctl perf profile, who don't have an active token receive the following message:

➜  ~ mesheryctl perf profile
Error: failed to make a request.Get "/": stopped after 10 redirects.
See https://docs.meshery.io/reference/mesheryctl/perf/profile for usage details

This behavior is true of a number of other commands. Each of the app, pattern, mesh, perf`.... should all apply the same logic and UX to the user - https://github.com/meshery/meshery/blob/2bf19d36cfd924c9c2e07fbb8686c975689309c5/mesheryctl/internal/cli/root/system/check.go#L489

Desired Behavior

Users should be informed of their inactive token and informed to run mesheryctl system login.

Acceptance Tests

  • 1. All perf commands apply this same check and UX.
  • 2. All mesh commands apply this same check and UX.
  • 3. All app commands apply this same check and UX.
  • 4. All pattern commands apply this same check and UX.

Contributor Resources

Contributor guide