Add config dump

[chris-olszewski]

• [x] docs (should solve #230)
• [x] tests
• [x] redo behavior to address new specs
• [x] refactor Addresses #226

[chris-olszewski]

@reconbot @southpolesteve does this look like the correct behavior?

[southpolesteve]

Cool. Can you make another issue and put it in a milestone? I wanna keep track of stuff that needs doing before we cut 4.0

On Wed, Jun 7, 2017 at 9:14 AM, Chris Olszewski notifications@github.com wrote:

@chris-olszewski commented on this pull request.

In src/commands/config/dump.js https://github.com/bustle/shep/pull/233#discussion_r120620713:

+import configDump from '../../config-dump' +import * as load from '../../util/load' +import merge from 'lodash.merge' + +export const command = 'dump [env]' +export const desc = 'Prints all common environmental variables and differences' +export function builder (yargs) {

• return yargs
• .pkgConf('shep', process.cwd())
• .boolean('json')
• .describe('json', 'Formats output as JSON')
• .example('shep config dump beta', 'Print to console all environment variables of environment beta in JSON format') +}

• +export async function handler (opts) {

• const envs = await load.envs()

I was going to switch the env behavior in another pr that I'm working on

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bustle/shep/pull/233#discussion_r120620713, or mute the thread https://github.com/notifications/unsubscribe-auth/AAcxaABSK4FmNM5L4sMSmQcdCXq0HeBoks5sBqJOgaJpZM4NmZh2 .

[chris-olszewski]

Going to just roll this into the larger env rework/4.0 PR