41ac7aeec2
This change allows any middleware that use oslo.config to be configured via paste-deploy, like the cors does. Related-bug: #1482086 Change-Id: Ibb3e951b45b51c9bc602c9113df18a58226d92d1
1.5 KiB
1.5 KiB
Middlewares and configuration
Middlewares can be configured in multiple fashion depending of the application needs. Here is some use-cases:
Configuration from the application
The application code will looks like:
from oslo_middleware import sizelimit
from oslo_config import cfg
conf = cfg.ConfigOpts()
app = sizelimit.RequestBodySizeLimiter(your_wsgi_application, conf)Configuration with paste-deploy and the oslo.config
The paste filter (in /etc/my_app/api-paste.ini) will looks like:
[filter:sizelimit]
paste.filter_factory = oslo_middleware.sizelimit:RequestBodySizeLimiter.factory
# In case of the application doesn't use the global oslo.config
# object. The middleware must known the app name to load
# the application configuration, by setting this:
# oslo_config_project = my_appThe oslo.config file of the application (eg: /etc/my_app/my_app.conf) will looks like:
[oslo_middleware]
max_request_body_size=1000Configuration with pastedeploy only
The paste filter (in /etc/my_app/api-paste.ini) will looks like:
[filter:sizelimit]
paste.filter_factory = oslo_middleware.sizelimit:RequestBodySizeLimiter.factory
max_request_body_size=1000This will override any configuration done via oslo.config
Note
healtcheck middleware does not yet use oslo.config, see healthcheck_plugins