ddecrulle opened a new issue, #3930:
URL: https://github.com/apache/polaris/issues/3930
### Describe the bug
The Helm chart exposes a `cors` section in `values.yaml` to configure CORS
for Polaris. However, the ConfigMap template generates all
`quarkus.http.cors.*` properties but omits `quarkus.http.cors.enabled=true`,
which is required by Quarkus to actually activate the CORS filter.
### To Reproduce
1. Deploy Polaris with the Helm chart and configure CORS:
```yaml
cors:
allowedOrigins: ["http://localhost:5173";]
allowedMethods: ["GET", "POST", "PUT", "DELETE", "PATCH", "OPTIONS"]
```
2. Send a CORS preflight request:
```bash
curl -v -X OPTIONS http:///api/catalog/v1/config \
-H "Origin: http://localhost:5173"; \
-H "Access-Control-Request-Method: GET"
```
### Actual Behavior
The generated ConfigMap contains e.g.
`quarkus.http.cors.origins=http://localhost:5173` but not
`quarkus.http.cors.enabled=true`. Quarkus requires this property to enable the
CORS filter — without it, all other CORS properties are ignored.
### Expected Behavior
When any `cors.*` value is set in `values.yaml`,
`quarkus.http.cors.enabled=true` should automatically be added to the generated
`application.properties`.
### Additional context
Until this is fixed, use `advancedConfig` to manually set the missing
property:
```yaml
advancedConfig:
quarkus.http.cors.enabled: "true"
cors:
allowedOrigins: ["http://localhost:5173";]
allowedMethods: ["GET", "POST", "PUT", "DELETE", "PATCH", "OPTIONS"]
```
### System information
- Polaris Helm chart version: `1.3.0-incubating`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
