Enable CORS for all endpoints about serverless-cors-plugin

[erikerikson]

In case someone finds this issue too...
@breandr It is. Just create a s-templates.json file at the root of your project and give it something like:

{
  "corsTemplate": {
    "allowOrigin": "*",
    "allowHeaders": ["Content-Type", "X-Amz-Date", "Authorization", "X-Api-Key"]
  }
}

Then in your s-function.json:

{
  ...
  "custom": {
    "cors": "$${corsTemplate}"
  }
  ...
}

[erikerikson]

If you want to override it in a single or subset of functions, you can either create a s-templates.json as a peer to your s-function.json that redefines corsTemplate or you can just not use the template at all.

[brettstack]

Thanks, that's good to know. But what I was really hoping for was a "define once" solution. The template helps with reducing duplication, but ideally there would be no duplication and the functions would just inherit from the custom property in s-project.json. I'm new to serverless and not familiar with the patterns, so maybe this is a request for serverless core.

[joostfarla]

@breandr previously (SLS < 0.5), you could also set the policy on the component level. Since the component concept has been dropped, it was required to set the policy on each function (with or without using templates).

I've just added support for setting the configuration on the project level. It's available in v0.4.1!

[brettstack]

So good! Thanks mate.

On Sun, 27 Mar 2016, 4:05 a.m. Joost Farla, [email protected]
wrote:

@breandr https://github.com/breandr previously (SLS < 0.5), you could
also set the policy on the component level. Since the component concept has
been dropped, it was required to set the policy on each function (with or
without using templates).

I've just added support for setting the configuration on the project
level. It's available in v0.4.1!

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#21 (comment)