Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
ryanmt opened this issue Apr 25, 2017 · 1 comment
Open

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

ryanmt opened this issue Apr 25, 2017 · 1 comment

Comments

@ryanmt
Copy link

ryanmt commented Apr 25, 2017

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.

@abetomo
Copy link
Contributor

abetomo commented Jul 5, 2017

@ryanmt configFile is an option to specify environment variables.
What should I do in case of package?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants