-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use custom cors configuration #88
Comments
If you think this is a use case not currently covered well enough by: --no-config-change and the |
Sorry, I have not (for some reason) seen this comment until now. I'll see if I can take some time to submit a PR for this. :) |
@hequ Awesome! Thank you! As long as you take a look at those two options and confirm for me that it'll be adding new functionality here I'm 100% open to this. Sounds like a good addition from first glance that I don't think we have in the plugin. |
Allow specifying a custom CORS configuration file resolves #88
Allow specifying a custom CORS configuration file resolves #88
🎉 This issue has been resolved in version 4.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This is a:
Current behavior (if any)
Serverless-finch will override s3 bucket CORS configuration or it does not touch the configuration at all.
Proposed behavior
User can provide custom CORS configuration for the bucket the same way as
bucketPolicyFile
works.Proposed implementation details (optional)
Add new configuration setting
bucketCorsConfiguration
which would be the path to cors configuration .json file.I have a proposal about how this could work if this is something that could be considered to be added in the future.
Justification
The project I'm currently working needs special cors configuration for the SPA to work correctly. We use serverless-finch but we have had to disable the cors configuration override since it would break our deployment every time. It would be great to manage the CORS settings with finch as well.
The text was updated successfully, but these errors were encountered: