It seems that this plugin doesn't work with serverless-offline, regardless of the order in which the plugins are called.
For example, when I run the package command, I get the parsing warning but then the $forEach are replaced, whereas when I run sls offline, I only get the parsing warning, without the $forEach modifications:
With sls package :
> sls package
Warning: Invalid configuration encountered
at 'functions.companiesCreate.environment': unrecognized property '$forEach'
at 'functions.companiesDelete.environment': unrecognized property '$forEach'
Learn more about configuration validation here: http://slss.io/configuration-validation
Packaging my-package for stage local (eu-west-1)
✔ Found and replaced 2 $forEach matches
With sls offline :
> sls offline start --stage local --httpPort 8001 --lambdaPort 9001
Warning: Invalid configuration encountered
at 'functions.companiesCreate.environment': unrecognized property '$forEach'
at 'functions.companiesDelete.environment': unrecognized property '$forEach'
Learn more about configuration validation here: http://slss.io/configuration-validation
Warning: No external modules needed
Starting Offline at stage local (eu-west-1)
Offline [http for lambda] listening on http://localhost:9001
I try to forEach on env variables on my lambdas but it's correctly available after package, but not in serverless-offline, only for $forEach part :
Hello,
It seems that this plugin doesn't work with serverless-offline, regardless of the order in which the plugins are called.
For example, when I run the package command, I get the parsing warning but then the
$forEach
are replaced, whereas when I runsls offline
, I only get the parsing warning, without the$forEach
modifications:With
sls package
:With
sls offline
:I try to forEach on env variables on my lambdas but it's correctly available after package, but not in serverless-offline, only for
$forEach
part :Is it possible to make it compatible with serverless-offline in order to keep the same logic between local development and deployment?