Merged
Conversation
rselbach
approved these changes
Jul 31, 2023
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.
🛠️ Description
SDK can authenticate using a credential file. The credential file can specify service principal credentials or workload identity provided credentials.
🔗 External Links
HCP-378 RFC
👍 Definition of Done
Ran the following test program:
I wrote a valid config file to
~/.config/hcp/cred_file.json:Running the program printed a valid token.
I then moved the cred_file.json to
cred_file2.jsonand ran the program again. It tried to retrieve the token via the browser as expected.I then ran
HCP_CRED_FILE=~/.config/hcp/cred_file2.json ./awsand it again printed a valid token from workload identity federation.