Our middleware will be in the middlewares::groups::User and will be called after headers_propagator middleware. For more information about middlewares order:
The static yaml config of middleware. You must add middleware to the config grpc-server-middlewares-pipeline, otherwise the middleware will be disabled everywhere.
grpc-server-meta-filter:
headers:
- global-header
grpc-server-middlewares-pipeline:
middlewares:
grpc-server-meta-filter: # register the middleware in the pipeline
You can override a middleware config like overriding an enabled option.
Example.
grpc-server-meta-filter:
headers:
- global-header
grpc-server-middlewares-pipeline:
middlewares:
grpc-server-meta-filter: # register the middleware in the pipeline
enabled: true
some-service:
middlewares:
grpc-server-meta-filter:
# The middleware of this service will get this header instead of 'global-header'
headers:
- specific-header
Note
Imagine there are more options but you override only headers. Values of other options will be taken from a global config (from grpc-server-middlewares-pipeline)