serverless / serverless/serverless
AWS API Gateway: Support for W3C conform multiple CORS origins
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46.9k
- Forks
- 5.7k
- Avg merge
- 10h 7m
- Merged PRs (30d)
- 57
Description
This is a Feature Proposal
Description
This is a follow-up issue on https://github.com/serverless/serverless/issues/2476 since we've implemented the origin config parameter to make it possible to define one origin per event definition (as API Gateway proposes it).
However sometimes users might want to define multiple origins. We should discuss this feature in more-depth in this issue since it might introduce some implementation challenges do to lack of direct support via CloudFormation.
More discussion about this can be found here.
/cc @alexcasalboni @HyperBrain @jokeyrhyme
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked discussion in issue #2476, especially the referenced comment, and review how the existing origin configuration supports one origin per event definition. Clarify the desired multiple-origin behavior and the CloudFormation limitations before choosing an implementation. No files, tests, or concrete completion criteria are named in this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100