You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The plugin seems to ignore artifacts that are set inside a individual function in the serverless.yml.
It still creates it's own artifact and uploads this, which is not the expected behaviour.
In my case the artifact is to massive for an lambda@edge function; max 10Kb
Is there a way to use the set artifact and not create/pack one or this a Bug?
Configs
serverless.yml
webpack:
includeModules:
forceExclude:
- aws-sdk
- core-node-sdk
plugins:
- "@silvermine/serverless-plugin-cloudfront-lambda-edge"
- serverless-webpack
- serverless-latest-layer-version
- serverless-deployment-bucket
package:
individually: true
patterns:
- "!node_module/**"
functionLambdaAtEdge:
...rest
package:
artifact: 'path-to-some-artifact-file.zip' # my special artifact which is 1Kb
individually: true
lambdaAtEdge:
distribution: myCloudfront
eventType: 'origin-request'
function2:
name: function2
package: # not set
This is a Bug Report / Question
Description
The plugin seems to ignore artifacts that are set inside a individual function in the serverless.yml.
It still creates it's own artifact and uploads this, which is not the expected behaviour.
In my case the artifact is to massive for an lambda@edge function; max 10Kb
Is there a way to use the set artifact and not create/pack one or this a Bug?
Configs
serverless.yml
webpack.config.js
verbose out of config:
Additional Data
The text was updated successfully, but these errors were encountered: