Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support METADATA operator in header mutation #34671

Closed
guydc opened this issue Jun 11, 2024 · 3 comments
Closed

Support METADATA operator in header mutation #34671

guydc opened this issue Jun 11, 2024 · 3 comments
Labels
enhancement Feature requests. Not bugs or questions. stale stalebot believes this issue/PR has not been touched recently

Comments

@guydc
Copy link

guydc commented Jun 11, 2024

Title: Support METADATA operator in header mutation

Description:
The METADATA formatter operator, provided by the metadata formatter extension is planned to replace existing built-in access log operators such as DYNAMIC_METADATA, CLUSTER_METADATA, etc. The METADATA operator should also be supported in the header value of the route *_headers_to_add feature.

Currently, envoy rejects the METADATA operator in header values with the following error: Not supported field in StreamInfo: METADATA, while operators like DYNAMIC_METADATA, CLUSTER_METADATA are supported.

@guydc guydc added enhancement Feature requests. Not bugs or questions. triage Issue requires triage labels Jun 11, 2024
@alyssawilk alyssawilk removed the triage Issue requires triage label Jun 13, 2024
@mathetake
Copy link
Member

Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label Jul 29, 2024
Copy link

github-actions bot commented Aug 5, 2024

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature requests. Not bugs or questions. stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants