Script Subcommand for emitting environment variables - #201
Merged
Conversation
srizzling
force-pushed
the
script-subcommand
branch
from
July 26, 2018 06:24
cde2b18 to
933953a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi!
I have added a new subcommand called
script, this will allow users to emitting environment variables into their shell.Sometimes this is useful for passing into docker containers as a way to authenticate within a container, without having to do the login process within the container itself, and probably other use cases as well.
Changes:
Adding new script subcommand, should be able to emit a script that can be
eval'd or invoked to source a terminal with session credsUpdated
README.mdwith a splash of formatting and Table of Contents, since its actually quite large, and would help people new to the project.