)]}'
{"etc/cyborg/api-paste.ini":[{"author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"bd6e9eabc672796d086d3537c3099976d6245229","unresolved":false,"context_lines":[{"line_number":1,"context_line":"[pipeline:main]"},{"line_number":2,"context_line":"pipeline \u003d cors http_proxy_to_wsgi request_id authtoken api_v2"},{"line_number":3,"context_line":""},{"line_number":4,"context_line":"[app:api_v2]"},{"line_number":5,"context_line":"paste.app_factory \u003d cyborg.api.app:app_factory"}],"source_content_type":"text/x-properties","patch_set":1,"id":"f77ec53a_59dd2356","line":2,"updated":"2026-07-09 02:33:11.000000000","message":"The change adds the http_proxy_to_wsgi middleware to the API pipeline and registers its oslo.config namespace, which is an operations-facing change. No release note was added to inform operators of the new capability and how to enable it.\n\n**Severity**: SUGGESTION | **Confidence**: 0.8\n\n**Benefit**: Operators deploying Cyborg behind load balancers or reverse proxies may not be aware that they now need to set [oslo_middleware]/enable_proxy_headers_parsing \u003d True to leverage this middleware. A release note would surface this capability and its configuration during upgrade reviews.\n\n**Recommendation**:\nAdd a release note under releasenotes/notes/ describing the new middleware addition, for example: --- other: - | The ``http_proxy_to_wsgi`` middleware from ``oslo_middleware`` has been added to the Cyborg API pipeline. This allows the API to correctly detect client endpoint information (protocol, host) when deployed behind reverse proxies. To enable it, set ``[oslo_middleware]/enable_proxy_headers_parsing \u003d True`` in the configuration file.","commit_id":"ab3b5d70471b384a867efd9542c55bb709dce4fa"}]}