Serverless Stack

am I correct in thinking that `stack.setDefaultFunctionProps()` is the same thing as `app.setDefaultFunctionProps()`, except it only applies to functions created within that stack?

I recently found out that if you use both they merge with each other

I think we need better naming on those functions, I assumed it fully override (eg environment variables)

yeah.. that’s what I was thinking. so the app level sets defaults for all functions, and then stack level will override

yeah you can call it multiple times to load up seevral environment variables.

and that’s exactly my use case :smile: I needed some global ones like `STAGE` and `SENTRY_DSN`, but then one stack in particular needed a GraphQL endpoint URL

wait guys.. i don’t think there’s a `stack.setDefaultFunctionProps()`:flushed:

```    scope.setDefaultFunctionProps({
      bundle: {
        // sharp is a binary, and we have it in a Lambda layer, so exclude it
        externalModules: ['sharp'],
      },
      environment: {
        GRAPHQL_ENDPOINT_URL: props!.appSyncApi.url,
      },
    });```


and that `GRAPHQL_ENDPOINT_URL` shows up in only the functions in that stack. lemme double-check

I got confused because I saw a discussion about adding stack.setDefaultFunctionProps and though it existed

but look at this. here’s a function outside my MediaProcessor stack:

Is it possible that stack gets added before?

That function might get created before the other stack adds more defaults

hmm. yeah, this is the last stack out of the 3

sorry for the confusion! it would’ve been `this.setDefaultFunctionProps()` in the stack constructor, obviously

ok, so now I vote for this feature :laughing:

Seperately, was there a reason we named it `scope` instead of `app` <@U01JVDKASAC>?

yeah, good point. I’m gonna rename that to `stack` in my stack definitions

~You can technically create ur own Construct, and in there create ie. `sst.Api`, and the scope would be the outer Construct~
You can technically create ur own wrapper (ie. if you are using the CodePipeline) and you create stacks in there, and the scope would be the Pipeline

It’s not a use case I’ve come across often.

I'll make an issue for stack.setDefaultFunctionProps - I've seen this come up before