We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It is confusing to have configFile as an option to package that doesn't do the same thing as your deploy tooling.
configFile
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.
The text was updated successfully, but these errors were encountered:
@ryanmt configFile is an option to specify environment variables. What should I do in case of package?
package
Sorry, something went wrong.
pacakage
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: