Skip to content

[Transformer] Disable CORS at springboot

Arturo Hernandez [EPAM] requested to merge ah/adminui_ts into master

Type of change

  • Bug Fix
  • Feature
  • Enhancement

Does this introduce a change in the core logic?

  • [YES]

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Does this introduce a breaking change?

  • [NO]

What is the current behavior?

Whenever we need to integrate the gcz with admini-ui, we need to provide a set of CORS headers, but this is managed at istio level, not at service level, the service itself should not manage this if it is behind a reverse-proxy.

If we setup the cors at istio/nginx/lb at current implementation, admin-ui integration will still fail due bootspring web response configuration.

What is the new/expected behavior?

GCZ shouldn't set the CORS headers.

Have you added/updated Unit Tests and Integration Tests?

N/A

Any other useful information

Istio/nginx/loadbalancer should be in charge of setup the CORS headers.

Merge request reports