-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Dynamic Metadata for External Processing Filters Similar to Dynamic Metadata for External Authorization #19881
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
Comments
Basically what this says on the tin. I'd be happy to work on this but I'd like to ask the code owners what they think about this. I am planning on basically just porting the behavior from ext_authz filters to ext_proc filter. |
+1 on this, having a similar use case, using "header to metadata" filter instead. @gbrail any thoughts about this? |
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. |
I'm ready to start work on this. @pgeler can you elaborate more about your use case? |
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. |
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. |
Sorry to resurrect but I believe this would still be valuable If additional specifications are needed, I would describe them as follows: Background: Desire/suggestion: |
Title: Dynamic Metadata for External Processing Filters
Description:
Dynamic Metadata emissions for ext_proc like dynamic metadata in ext_authorization
[optional Relevant Links:]
>Any extra documentation required to understand the issue.
The text was updated successfully, but these errors were encountered: