[Utility] Push and pull heroku environment variables to your local env
Bot releases are hidden (Show)
https://github.com/xavdid/heroku-config/compare/v1.6.2...v1.6.3
Published by xavdid almost 2 years ago
https://github.com/xavdid/heroku-config/compare/v1.6.1...v1.6.2
Published by xavdid over 2 years ago
https://github.com/xavdid/heroku-config/compare/v1.6.0...v1.6.1
Published by xavdid over 2 years ago
--pipeline-name
and --pipeline-stage
flags (#26).env
file to link to this repolodash
dependencyhttps://github.com/xavdid/heroku-config/compare/v1.5.3...v1.5.4
https://github.com/xavdid/heroku-config/compare/v1.5.2...v1.5.3
Published by xavdid almost 8 years ago
When pushing, you can now specify the -c | --clean
flag to erase destination variables if they weren't present in the file you're reading from. Use this cautiously!
Thanks to @aaroncraigongithub for the PR!
Published by xavdid about 8 years ago
This release bring a couple of neat conveniences that should make the overall experience of using the plugin more enjoyable!
By default, heroku adds a NODE_ENV
, RACK_ENV
, or equivalent set to production
. Typically this is great, but when pulling configs it's an easy way to accidentally run your app in the wrong mode locally. If it sees a key like this coming by, it'll prompt you to [d]elete | [i]gnore | [a]lways (delete) | [n]ever (delete)
that key for that app. These settings are stored in (the created as soon as you use it) .heroku_config_settings.json
There's now a lot more options for how you want to format your local file. See the readme for more info.