Skip to content

[local-preview] Better messaging in CLI output on Limitations and Next steps #11316

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

Closed
Tracked by #9075
lucasvaltl opened this issue Jul 12, 2022 · 2 comments
Closed
Tracked by #9075

Comments

@lucasvaltl
Copy link
Contributor

Is your feature request related to a problem? Please describe

We want to be very explicit about what the local preview can and cannot do. We will do this in our documentation, however not everyone reads this.

Describe the behaviour you'd like

As such, we should also use the CLI output as a tool to:

  • Make clear what the limitations are (performance, missing features)
  • What to do abot this (use a reference archtiecture)
  • What to do next assuming the process has run to completion (enter domain)

Describe alternatives you've considered

  • Only do this in the documentation - not everyone reads this.

Additional context

@Pothulapati
Copy link
Contributor

More feedback on this https://gitpod.slack.com/archives/C0408T1QD6W/p1664349935299199, when we fail on checking prerequisites it would be nice to show the user the specific reason!

@lucasvaltl
Copy link
Contributor Author

This is somewhat solved by #13123 - will close this for now. @Pothulapati feel free to reopen if you think this is still relevant even with the fixes mentioned above.

Repository owner moved this from 🧊Backlog to ✨Done in 🚚 Security, Infrastructure, and Delivery Team (SID) Oct 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

2 participants