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.
It is confusing to have
configFileas 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.