Prefer --api-key over STRIPE_API_KEY#1591
Open
EfeDurmaz16 wants to merge 1 commit into
Open
Conversation
|
|
1 similar comment
|
|
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.
Summary
--api-keyoverride take precedence overSTRIPE_API_KEYSTRIPE_API_KEYas the fallback before persisted config/keychain credentialswhoamikey classification and regression tests for flag/env precedenceCloses #1581.
Testing
go test ./pkg/config -run TestGetAPIKeyenv HOME=$(mktemp -d) go test ./pkg/cmd -run TestWhoamienv HOME=$(mktemp -d) go test ./pkg/config ./pkg/cmd -run 'TestGetAPIKey|TestWhoami'Note: a non-isolated local
go test ./pkg/config ./pkg/cmdreads my machine's existing Stripe config and also hits an existingTestGetLoginEmptytemplate-state failure. The focused regression tests above pass with an isolatedHOME.