-
Notifications
You must be signed in to change notification settings - Fork 100
Open
Labels
request/newRequest: Indicates a new request that has been submitted and awaits initial triageRequest: Indicates a new request that has been submitted and awaits initial triagetype/bugType: Something is not working as expectedType: Something is not working as expected
Description
Just a bunch of things that i experienced struggling with a customer:
- Can’t tell what host you’re talking to
- Not obvious that skew for versions
- Bad version skew (server to client, client to server) - just catch and say “incompatible”
- Can’t refresh tokens
- Term “token” confusing - i know it’s API_KEY, but maybe something else? man, it was so hard to explain this
- “404” for not found for bad auth
- More skew issues: Error: failed request: no common authentication method: client supports [ask challenge], server supports []
- “https:” vs. “nothing” in api-host => be friendly about not using the right thing.
- “Labels” not being on the same indentation as Compute is weird … but i guess it makes sense. Would be great if we detected “Labels” was under orchestrator or compute, that’s an error.
Metadata
Metadata
Assignees
Labels
request/newRequest: Indicates a new request that has been submitted and awaits initial triageRequest: Indicates a new request that has been submitted and awaits initial triagetype/bugType: Something is not working as expectedType: Something is not working as expected