Fix command line arguments and non-AWS profile scoped arguments when an AWS profile is not present in the config. #196
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.
viper.Get()
returns an empty string when an AWS profile exists in the config, but has not been set.viper.Get()
returns nil when the AWS profile does not exist in the config or the config file does not exist. viper.viper.IsSet()
returns will return false when the config/profile does not exist, but always returns true when the profile exists (irrelevant of whether the actual key is defined).Combining these two means that:
Fixes #194
Addresses issue in #192