Add EXPORT functionality

[reskin89]

As a user, I'd like to be able to use this as a normal environment loader as well if I so choose, such as using eval in front of it, so that the variables get the export keyword prepended.

Say I have many environment files that I switch between for local development, they may not contain secrets, but I don't necessarily want to manage them with generic Linux env files, and I'd like to be able to put the yml in VC for other teammates to replicate that non sensitive environment.

While using source is an option, if I'm going to use nv for secrets management as well, it may make sense to just use one tool.

I'm sure there are other applications to doing it that way as well or having that option, as I've used https://github.com/comcast/buildenv-tool with Makefiles this way for repeatable deployment and development as well.

[maxnorth]

Hey, @reskin89, the options are still under-documented (working on that), but if I'm understanding the request correctly, this functionality is currently available. The print command supports an output format called shell which will print as export KEY="value". You can then use that as eval $(nv print -o shell) to load vars into the current session. Alternately, you could start a new session with nv -- bash, which can be cleaner for managing sessions, since you can easily reset by exiting (especially handy if often switching between target environments).

[maxnorth]

Also heads up the currently installable version has an issue that only causes it to print values that were resolved and not everything loaded from .env files. Fix for that should be available shortly.

[maxnorth]

Also heads up the currently installable version has an issue that only causes it to print values that were resolved and not everything loaded from .env files. Fix for that should be available shortly.

Just fixed this, there's a new release available - https://github.com/maxnorth/nv/releases/tag/v0.1.1