serverless / serverless/serverless
"sls login" results in warnings "unsupported configuration format" regarding ${param:....} in the environment - section
Open
@mtin79 is already working on this.
Since Nov 2, 2020.
question
- Dominant language
- JavaScript
- Stars
- 46.9k
- Forks
- 5.7k
- Avg merge
- 10h 7m
- Merged PRs (30d)
- 57
Description
Hi there,
we upgraded from serverless version 1 to version 2.
after executing "sls login" we get the following warnings display:
npx sls login
Serverless: Configuration warning:
Serverless: at 'provider.environment.DB_ENDPOINT': unsupported configuration format
Serverless: at 'provider.environment.DB_PORT': unsupported configuration format
Serverless: at 'provider.environment.DB_NAME': unsupported configuration format
Serverless: at 'provider.environment.DB_USERNAME': unsupported configuration format
Serverless: at 'provider.environment.DB_PASSWORD': unsupported configuration format
Serverless: at 'provider.environment.ORDERARTICLES_S3_BUCKET': unsupported configuration format
Serverless: at 'provider.environment.ORDERARTICLES_FILENAME_EXTENSION': unsupported configuration format
Serverless: at 'provider.environment.ORDERARTICLES_FILEPATH': unsupported configuration format
Serverless: at 'app': should match pattern "^[a-z0-9][a-z0-9-]{1,37}[a-z0-9]$"
Serverless:
Serverless: Learn more about configuration validation here: http://slss.io/configuration-validation
Serverless:
Serverless: Logging you in via your default browser...
Serverless: You sucessfully logged in to Serverless.
the serverless.yml in the warned about section looks like this:
provider:
name: aws
runtime: nodejs12.x
region: ${opt:region, "eu-central-1"}
stage: ${opt:stage, "development"}
environment:
DB_ENDPOINT: ${param:DB_ENDPOINT}
DB_PORT: ${param:DB_PORT}
DB_NAME: ${param:DB_NAME}
DB_USERNAME: ${param:DB_USERNAME}
DB_PASSWORD: ${param:DB_PASSWORD}
ORDERARTICLES_S3_BUCKET: ${param:ORDERARTICLES_S3_BUCKET}
ORDERARTICLES_FILENAME_EXTENSION: ${param:ORDERARTICLES_FILENAME_EXTENSION}
ORDERARTICLES_FILEPATH: ${param:ORDERARTICLES_FILEPATH}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.