You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title: Remove first then add when adding a scope which has the same key as a to-be-deleted scope.
Description:
A new scope may have the same scope key as a to-be-deleted existing scope, in which case we should not raise an scope key conflict error.
Repro steps:
push -1: { scope A: keyA }
push -2: { Scope B: keyA } (in StoW API, this means deletion of "Scope A").
now in the delta form onConfigUpdate, we will report conflict error as the new scopeB 's "keyA" conflicts with the existing scopeA's key.
The text was updated successfully, but these errors were encountered:
…void scope key conflict. (#9366)
Remove scopes first then add scopes to avoid scope key conflict when a new scope has the same key as an existing scope
Risk Level: MID
Testing: unit test
Docs Changes:
Release Notes:
Fixes: #9349
Signed-off-by: Xin Zhuang <stevenzzz@google.com>
prakhag1
pushed a commit
to prakhag1/envoy
that referenced
this issue
Jan 3, 2020
…void scope key conflict. (envoyproxy#9366)
Remove scopes first then add scopes to avoid scope key conflict when a new scope has the same key as an existing scope
Risk Level: MID
Testing: unit test
Docs Changes:
Release Notes:
Fixes: envoyproxy#9349
Signed-off-by: Xin Zhuang <stevenzzz@google.com>
Signed-off-by: Prakhar <prakhar_au@yahoo.com>
Bug Template
Title: Remove first then add when adding a scope which has the same key as a to-be-deleted scope.
Description:
Repro steps:
push -1: { scope A: keyA }
push -2: { Scope B: keyA } (in StoW API, this means deletion of "Scope A").
now in the delta form onConfigUpdate, we will report conflict error as the new scopeB 's "keyA" conflicts with the existing scopeA's key.
The text was updated successfully, but these errors were encountered: