Is there an existing issue for this?
Current behavior
When Swagger/OpenAPI is enabled in the self-hosted Helm deployment using:
env:
enable_drf_spectacular: true
the Swagger UI endpoint loads:
However, the Swagger UI static assets are requested from:
/static/drf_spectacular_sidecar/...
The current Helm-generated ingress does not include a route for /static/drf_spectacular_sidecar, so these requests fall back to the frontend web service instead of the API service.
As a result, the web service returns HTML instead of CSS/JS, causing the Swagger UI page to stay blank.
Steps to reproduce
The ingress currently generates routes like:
/ -> plane-app-web
/spaces/ -> plane-app-space
/god-mode/ -> plane-app-admin
/api/ -> plane-app-api
/auth/ -> plane-app-api
/live/ -> plane-app-live
/graphql/ -> plane-app-api
/marketplace/ -> plane-app-api
/silo/ -> plane-app-silo
There is no route for:
/static/drf_spectacular_sidecar/
Environment
Production
Browser
Google Chrome
Variant
Self-hosted
Version
2.6.0
Is there an existing issue for this?
Current behavior
When Swagger/OpenAPI is enabled in the self-hosted Helm deployment using:
the Swagger UI endpoint loads:
However, the Swagger UI static assets are requested from:
The current Helm-generated ingress does not include a route for
/static/drf_spectacular_sidecar, so these requests fall back to the frontend web service instead of the API service.As a result, the web service returns HTML instead of CSS/JS, causing the Swagger UI page to stay blank.
Steps to reproduce
The ingress currently generates routes like:
There is no route for:
Environment
Production
Browser
Google Chrome
Variant
Self-hosted
Version
2.6.0