keronmotorcycle.blogg.se - Npm serverless-plugin-warmup not working

#NPM SERVERLESS PLUGIN WARMUP NOT WORKING CODE#
#NPM SERVERLESS PLUGIN WARMUP NOT WORKING ZIP#

(/Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/bin/serverless.js:47:1)Īt Function.executeUserEntryPoint (internal/modules/run_main.js:71:12)Īt internal/main/run_main_module.

(/Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/scripts/serverless.js:50:4)Īt Module._compile (internal/modules/cjs/loader.js:1137:30)Īt Object.Module._extensions.js (internal/modules/cjs/loader.js:1157:10)Īt Module.load (internal/modules/cjs/loader.js:985:32)Īt Function.Module._load (internal/modules/cjs/loader.js:878:14)Īt Module.require (internal/modules/cjs/loader.js:1025:19)Īt require (internal/modules/cjs/helpers.js:72:18)Īt Object. (/Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/plugins/aws/package/compile/functions/index.js:681:16)Īt (domain.js:483:12)Īt /Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/node_modules/graceful-fs/graceful-fs.js:282:14Īt /Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/node_modules/graceful-fs/graceful-fs.js:333:16Īt FSReqCallback.oncomplete (fs.js:156:23)Īt pileFunction (/Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/plugins/aws/package/compile/functions/index.js:103:25)Īt /Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/plugins/aws/package/compile/functions/index.js:623:62Īt pileFunctions (/Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/plugins/aws/package/compile/functions/index.js:623:22)Īt Object.package:compileFunctions (/Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/plugins/aws/package/compile/functions/index.js:32:12)Īt PluginManager.invoke (/Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/classes/PluginManager.js:510:22)Īt PluginManager.spawn (/Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/classes/PluginManager.js:530:17)Īt /Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/plugins/deploy/deploy.js:122:50Īt Object.before:deploy:deploy (/Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/plugins/deploy/deploy.js:102:22)Īt /Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/classes/PluginManager.js:510:55Īt /Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/classes/PluginManager.js:545:24Īt n (/Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/classes/PluginManager.js:545:8)Īt /Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/Serverless.js:168:33Īt n (/Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/lib/Serverless.js:155:74)Īt /Users/admin/.nvm/versions/node/v12.18.3/lib/node_modules/serverless/scripts/serverless.js:50:26Īt processImmediate (internal/timers.js:456:21)Īt Object. See the "Networking" section for more details.Error: Could not add file content to hash: Error: ENOENT: no such file or directory, open '/Users/admin/Projects/afterpay-bold-plugin/.build/.serverless/warmUpPlugin.zip'Īt ReadStream. Add a 1 second connect timeout to the AWS SDK If tracing is enabled at the provider level or at the warmer config level, the X-Ray client is automatically installed and X-Ray tracing is enabled. See "Permissions" section Support Tracing If no role is provided in the custom.warmup config, a default role with minimal permissions is created for each warmer.

sourceRaw Has been renamed to payloadRawĪutomatically creates a role for the lambda.

schedule schedule: rate(5 minutes) is equivalent to events: - schedule: rate(5 minutes).

The following legacy options have been completely removed: The permissions can also be added to all lambdas using setting the role to IamRoleLambdaExecution and setting the permissions in iamRoleStatements under provider (see ):ĭefault: # Name of the warmer, see above enabled: 'prod ' Removed legacy options The artifact option is especially useful in case your development environment allows you to generate a deployable artifact like Maven does for Java. Either you use artifact or include / exclude.

#NPM SERVERLESS PLUGIN WARMUP NOT WORKING ZIP#

ec2:DeleteNetworkInterface Resource: "* " Serverless won't zip your service if this is configured and therefore exclude and include will be ignored.

name Name of the generated warmer lambda (defaults to $ # and one more row for each function that must be warmed up by the warmer # Warmer lambda to manage ENIS (only needed if deploying to VPC, ).

You might want to keep it if you are doing some custom packaging (defaults to true)

#NPM SERVERLESS PLUGIN WARMUP NOT WORKING CODE#

cleanFolder Whether to automatically delete the generated code folder.

folderName Folder to temporarily store the generated code (defaults to.

The options are the same for all the warmers: schedule: cron(0/5 * ? * SAT-SUN *) concurrency: 1 verbose: false testWarmer: schedule: cron(0/5 8-17 ? * MON-FRI *) concurrency: 10 verbose: true logRetentionInDays: 10 outOfOfficeHoursWarmer: