Daniel

This would be nice. However deleting the associated lambda is a little tricky. If you refer to https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-delete-replicas.html, > You can delete a Lambda@Edge function only when the replicas of...

@macs91 Use next's [build time configuration ](https://github.com/zeit/next.js/#build-time-configuration). This is the recommended approach for managing environment config. in your pages.

> @danielcondemarin I tried it, but I see that it leaks env variables to the client... Given that I intend to store secrets I can't use that 😬 Ohh I...

@macs91 Could you share how you're accessing the env. config. in the page? i.e. on `getInitialProps` I'm guessing?

@macs91 Sounds incredibly easy to leak the secure config. by accident., so I'll be adding support for runtime only env. configuration via a `serverless.yml` input. Stay tuned 😄

@macs91 Found out today Lambda@Edge [doesn't support](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-requirements-limits.html#lambda-requirements-lambda-function-configuration) environment variables :/ Hopefully this will be supported / available soon! But for now you'll have to workaround it by using the build...

> Bummer! I didn't know that.. Hopefully they will announce support at re:Invent 😁 That's what I'm hoping. All I can do for now is [ask for it](https://twitter.com/dcondemarin/status/1181303348827492353) 🙂

@gbwashleybrown Did you have a look at `build.env` ? https://github.com/danielcondemarin/serverless-next.js#inputs It uses next's build time env variables as documented in https://nextjs.org/docs/api-reference/next.config.js/environment-variables

@Arditc It is not currently supported however I'd love to add support for it. In theory it shouldn't be too difficult assuming we can get [Helmet](https://github.com/helmetjs/helmet) working with plain Node...

Yeah I'm working exactly on this. Should have something ready this week. I think it would be easy to predefine new cache policies for [some](https://github.com/serverless-nextjs/serverless-next.js/blob/master/packages/serverless-components/nextjs-component/src/component.ts#L336) [of](https://github.com/serverless-nextjs/serverless-next.js/blob/master/packages/serverless-components/nextjs-component/src/component.ts#L349) the behaviours we've got...