router: Add do_formatting arg to responseHeaderTransforms #16529
router: Add do_formatting arg to responseHeaderTransforms #16529snowp merged 6 commits intoenvoyproxy:mainfrom
Conversation
Signed-off-by: Ashley Hedberg <ahedberg@google.com>
Signed-off-by: Ashley Hedberg <ahedberg@google.com>
snowp
left a comment
There was a problem hiding this comment.
Thanks, this seems reasonable to just a few nits.
Out of curiosity what is the use case for this?
Signed-off-by: Ashley Hedberg <ahedberg@google.com>
Signed-off-by: Ashley Hedberg <ahedberg@google.com>
ahedberg
left a comment
There was a problem hiding this comment.
Thanks, this seems reasonable to just a few nits.
Out of curiosity what is the use case for this?
We have an Envoy deployment where, at request time, we need to send the configured response header transformations to another (non-Envoy) service, which will apply them at response time. We don't want to evaluate the response header transformations at request time, as we need to convert any with the Envoy-style %PER_REQUEST_FORMAT% markers to the format the other service understands.
My initial PR adding this API should have done this, but I didn't realize the interaction at the time. My bad.
|
Ping @snowp ? Windows presubmit errors look unrelated to this change. |
|
Retrying Azure Pipelines: |
|
The Windows CI failures seem related: |
Signed-off-by: Ashley Hedberg <ahedberg@google.com>
Hmm, that was not the error I saw the first time. I think Windows is doing something weird now that I've switched this to |
Signed-off-by: Ashley Hedberg <ahedberg@google.com>
|
Dropping |
|
Retrying Azure Pipelines: |
…#16529) Signed-off-by: Ashley Hedberg <ahedberg@google.com>
Commit Message: Add do_formatting arg to responseHeaderTransforms
Additional Description: This change adds an additional argument,
bool do_formatting, toResponseEntry::responseHeaderTransforms. This allows callers to retrieve the original value instead of the evaluated/formatted value. The default value istrueto match existing behavior and prevents changes to existing callsites.Risk Level: low
Testing: unit tests
Docs Changes: doc updated
Release Notes: n/a
Platform Specific Features: n/a