heroku-config

• update readme 9c5b5d7
• don't try and delete heroku config vars (#33) b8a7a83
• Bump word-wrap from 1.2.3 to 1.2.4 (#36) dcd402d
• Bump decode-uri-component from 0.2.0 to 0.2.2 (#28) f93f7fe

https://github.com/xavdid/heroku-config/compare/v1.6.2...v1.6.3

• don't send keys that haven't changed during push. This should have no effect on existing workflows, since the duplicate writes would have had no effect anyway (#30) ab5dd2c

https://github.com/xavdid/heroku-config/compare/v1.6.1...v1.6.2

• Fix clean flag; thanks @icheko! (#27) ce42d38

https://github.com/xavdid/heroku-config/compare/v1.6.0...v1.6.1

• Add support for pipelines via --pipeline-name and --pipeline-stage flags (#26)
• Update header in the generated .env file to link to this repo
• bump lodash dependency

• fix: prioritize multi-line over normal regex d1213d8

https://github.com/xavdid/heroku-config/compare/v1.5.3...v1.5.4

• (fix) use platform agnostic home dir e220926

https://github.com/xavdid/heroku-config/compare/v1.5.2...v1.5.3

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!

This release bring a couple of neat conveniences that should make the overall experience of using the plugin more enjoyable!

Safely Pulling env

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

File flexibility

There's now a lot more options for how you want to format your local file. See the readme for more info.

Quiet mode added