Packaging doesn't allows the configFile but doesn't consume it

Open

#246 opened on Apr 25, 2017 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 35/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Tech stack: aws, javascript, node.js
Domain: cli, cloud

Research direction

Start by tracing the package command's handling of configFile and compare it with the deploy and run commands mentioned in the issue. The change is complete when packaging consumes the configured environment variables consistently with those commands; check any existing package-related tests if present.

Written by the indexing model from the issue text.

Description

enhancement

It is confusing to have configFile as an option to package that doesn't do the same thing as your deploy tooling.

I use your tool w/o the deploy feature, and this was a surprising inconsistency when I discovered that my env vars aren't packaged as I'd expected.

I would advocate packaging those as you do for deploy or run commands.

Dominant language: JavaScript
Stars: 1.4k
Forks: 185
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.