Describe the pull request
This pull request addresses an issue where uploads to S3 in the production environment are being blocked due to CORS (Cross-Origin Resource Sharing) issues. The fix involves changing the fetch mode to 'no-cors', thereby allowing these uploads to proceed without triggering CORS restrictions.
Checklist
[x] I have linked the relative issue to this pull request
[x] I have made the modifications or added tests related to my PR
[x] I have added/updated the documentation for my RP
[x] I put my PR in Ready for Review only when all the checklist is checked
Show Validation
```
Success! The configuration is valid.
```
Terraform Plan 📖 success
Show Plan
```
kubernetes_config_map.stud42_config: Refreshing state... [id=sandbox/stud42-config]
module.istio.kubectl_manifest.virtual_services["dev-s42-sandbox"]: Refreshing state... [id=/apis/networking.istio.io/v1alpha3/namespaces/sandbox/virtualservices/dev-s42-sandbox]
module.jwtks_service.kubernetes_service.app[0]: Refreshing state... [id=sandbox/jwtks-service]
module.jwtks_service.kubernetes_deployment.app[0]: Refreshing state... [id=sandbox/jwtks-service]
module.jwtks_service.kubernetes_horizontal_pod_autoscaler_v2.app[0]: Refreshing state... [id=sandbox/jwtks-service]
module.jwtks_service.kubernetes_manifest.certificate["grpc-internal"]: Refreshing state...
No changes. Your infrastructure matches the configuration.
Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
```
Describe the pull request This pull request addresses an issue where uploads to S3 in the production environment are being blocked due to CORS (Cross-Origin Resource Sharing) issues. The fix involves changing the fetch mode to 'no-cors', thereby allowing these uploads to proceed without triggering CORS restrictions.
Checklist
Breaking changes ? no