Allow more flexibility to GOOGLE_APPLICATION_CREDENTIALS parsing #415
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.
The GoogleAuth library supports creating credentials for multiple credential types. The current state of inspec-gcp limits users passing a
GOOGLE_APPLICATION_CREDENTIALS
file to only be able to use service accounts.Description
This allows users utilizing authentication types other than service accounts to pass an appropriate
GOOGLE_APPLICATION_CREDENTIALS
file. It is no longer recommended by Google to utilize a service account directly and Workload Identity Federation is the recommended replacement. I am trying to implement Workload Identity Federation in googleauth and utilize it with InSpec and this is one of the issues I encountered.Issues Resolved
This is relevant to the work I am doing in googleapis/google-auth-library-ruby#354