serverless / serverless/serverless
If specific file in `environments` is not available, don't continue with deploys
Open
Nobody has claimed this yet.
cat/dx
enhancement
needs feedback
- Dominant language
- JavaScript
- Stars
- 46.9k
- Forks
- 5.7k
- Avg merge
- 10h 7m
- Merged PRs (30d)
- 57
Description
Example
name: aws
runtime: nodejs6.10
stage: ${opt:stage, 'dev'}
timeout: 10
environment:
DEBUG: ${file(../config/${self:provider.stage}.yml):DEBUG}
If the YML file does not exist, throw an error and don't continue with deploys.
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.
Research direction
Start by tracing how the environment block resolves ${file(...)} references during deploys, using the example configuration as the reproduction case. Check the file-resolution and deploy entry points, then add or locate coverage for a missing stage-specific YAML file. Done means a missing file raises an error before deploys continue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100