Conversation
|
/test all |
|
Skipping CI for Draft Pull Request. |
|
@howardjohn: The following tests failed, say
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
This PR adds controls to which headers should be added to requests/responses. This solves (most of) istio/istio#17635, a common feature request. A prototype is implemented in istio/istio#37215. Open questions: * Naming bikeshed * Mesh config or proxy config or something else? Currently its in proxy config * Is a list of ENUMs the best way to represent this? it does allow a strange config like `[REQUEST_ID, REQUEST_ID]` but that can just rejected
|
@howardjohn: PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2022-02-08. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions. Created by the issue and PR lifecycle manager. |
This PR adds controls to which headers should be added to requests/responses. This solves (most of) istio/istio#17635, a common feature request. A prototype is implemented in istio/istio#37215. Open questions: * Naming bikeshed * Mesh config or proxy config or something else? Currently its in proxy config * Is a list of ENUMs the best way to represent this? it does allow a strange config like `[REQUEST_ID, REQUEST_ID]` but that can just rejected
This PR adds controls to which headers should be added to requests/responses. This solves (most of) istio/istio#17635, a common feature request. A prototype is implemented in istio/istio#37215. Open questions: * Naming bikeshed * Mesh config or proxy config or something else? Currently its in proxy config * Is a list of ENUMs the best way to represent this? it does allow a strange config like `[REQUEST_ID, REQUEST_ID]` but that can just rejected
This PR adds controls to which headers should be added to requests/responses. This solves (most of) istio/istio#17635, a common feature request. A prototype is implemented in istio/istio#37215. Open questions: * Naming bikeshed * Mesh config or proxy config or something else? Currently its in proxy config * Is a list of ENUMs the best way to represent this? it does allow a strange config like `[REQUEST_ID, REQUEST_ID]` but that can just rejected
This PR adds controls to which headers should be added to requests/responses. This solves (most of) istio/istio#17635, a common feature request. A prototype is implemented in istio/istio#37215. Open questions: * Naming bikeshed * Mesh config or proxy config or something else? Currently its in proxy config * Is a list of ENUMs the best way to represent this? it does allow a strange config like `[REQUEST_ID, REQUEST_ID]` but that can just rejected
This PR adds controls to which headers should be added to requests/responses. This solves (most of) istio/istio#17635, a common feature request. A prototype is implemented in istio/istio#37215. Open questions: * Naming bikeshed * Mesh config or proxy config or something else? Currently its in proxy config * Is a list of ENUMs the best way to represent this? it does allow a strange config like `[REQUEST_ID, REQUEST_ID]` but that can just rejected
* Add controls around injected headers This PR adds controls to which headers should be added to requests/responses. This solves (most of) istio/istio#17635, a common feature request. A prototype is implemented in istio/istio#37215. Open questions: * Naming bikeshed * Mesh config or proxy config or something else? Currently its in proxy config * Is a list of ENUMs the best way to represent this? it does allow a strange config like `[REQUEST_ID, REQUEST_ID]` but that can just rejected * address comments * xfcc
This PR adds controls to which headers should be added to requests/responses. This solves (most of) istio/istio#17635, a common feature request. A prototype is implemented in istio/istio#37215. Open questions: * Naming bikeshed * Mesh config or proxy config or something else? Currently its in proxy config * Is a list of ENUMs the best way to represent this? it does allow a strange config like `[REQUEST_ID, REQUEST_ID]` but that can just rejected
This PR adds controls to which headers should be added to requests/responses. This solves (most of) istio/istio#17635, a common feature request. A prototype is implemented in istio/istio#37215. Open questions: * Naming bikeshed * Mesh config or proxy config or something else? Currently its in proxy config * Is a list of ENUMs the best way to represent this? it does allow a strange config like `[REQUEST_ID, REQUEST_ID]` but that can just rejected
* Add controls around injected headers This PR adds controls to which headers should be added to requests/responses. This solves (most of) istio/istio#17635, a common feature request. A prototype is implemented in istio/istio#37215. Open questions: * Naming bikeshed * Mesh config or proxy config or something else? Currently its in proxy config * Is a list of ENUMs the best way to represent this? it does allow a strange config like `[REQUEST_ID, REQUEST_ID]` but that can just rejected * address comments * xfcc --------- Co-authored-by: John Howard <howardjohn@google.com>
Please provide a description of this PR: