Skip to content
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

Wrap errors from the API server #583

Closed
hausdorff opened this issue Jun 4, 2019 · 1 comment
Closed

Wrap errors from the API server #583

hausdorff opened this issue Jun 4, 2019 · 1 comment
Assignees
Labels
area/providers kind/enhancement Improvements or new features

Comments

@hausdorff
Copy link
Contributor

Reporting errors from the API server is a consistent source of friction, because it's not clear to users whether the problem is from Pulumi or their own code.

It should be trivial to fix this: call errors.Wrapf on every error returned from the API server, and add a message saying that Kubernetes itself is reporting something about your code.

This contributes to probably 50% of issues I encounter from new users. We should try to fix this in M24.

@hausdorff hausdorff added area/providers kind/enhancement Improvements or new features labels Jun 4, 2019
@hausdorff hausdorff added this to the 0.24 milestone Jun 4, 2019
@hausdorff
Copy link
Contributor Author

We probably also want to work on reporting await errors a little better. It's usually also unclear whether an await failure is pulumi or your code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/providers kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

3 participants