Repository navigation
Egress gateway answers a credential provider fault with 502, not 403 - #2706
Eric Curtin (ericcurtin) wants to merge 3 commits into
Conversation
|
Quentin Bisson (@QuentinBisson) PTAL, the agentgateway side can match this table. Thank you! |
|
LGTM from the issue side, the table matches what I proposed. agentgateway/agentgateway#3875 now mirrors this exactly. I'm not a maintainer here though, so this still needs a maintainer's review. |
|
Keith Mattix II (@keithmattix) Eitan Yarmush (@EItanya) PTAL when you get a chance. QuentinBisson confirmed the table matches what agentgateway will do. Thank you! |
|
#2555 is closed, do we still need this? |
|
Yes i closed the issue by mistake. This is still needed |
Signed-off-by: Eric Curtin <eric.curtin@docker.com>
04f1054 to
bdb9ed3
Compare
|
Rebased onto main, bdb9ed3. Davanum Srinivas (@dims) thank you, QuentinBisson confirmed it is still needed. Lior Lieberman (@LiorLieberman) Julian Gutierrez Oschmann (@juli4n) PTAL when you get a chance. Thank you! |
Signed-off-by: Eric Curtin <eric.curtin@docker.com>
32d2773 to
ff0c5f9
Compare
|
Quentin Bisson (@QuentinBisson) DCO sign-off fixed, no code changes. |
A provider
Internal,UnknownorUnimplementedor an unusable credential is now 502, andResourceExhaustedis a retryable 503.InvalidArgumentstays 403 since the provider rejected the URI. The config-error row is unchanged.Fixes #2555