-
Notifications
You must be signed in to change notification settings - Fork 223
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
Improve 403 Forbidden error case #10
Comments
As an aside, a nicer 404 is probably worth considering. Shall I file a separate issue? BTW, let's use support@pulumi.com for this, not your email address. |
Let's track both issues in this bug, though the fixes will require two very different approaches. Also, ack on the email address. Though I was hoping it would be my opportunity to look like a stock photo of somebody in tech support... |
From a conversation in the office:
|
Given that we plan to flip this to public roughly after 0.9, is it worth doing anything here? I propose we just close this out and spend our energy building the real deal. |
Propose keeping this open in case we need it for a bigger private preview in Jan/Feb |
Proposing we close this. When we do the private beta, we can just document the symptom for customers. Filed #72 for the 404 case. |
If you are not authorized to access the website (GitHub account authorized, but not on a whitelist) we should provide that information to the user. e.g. "You were not on any whitelisted GitHub organizations or email domains. Please contact chris@pulumi.com if you believe this is an error."
The text was updated successfully, but these errors were encountered: