Add new ServiceAccountCredentialsTemplate, mark ServiceAccountTemplate as deprecated #4
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 IAM API is deprecating its
SignJwt
andSignBlob
endpoints.This PR updates the
ServiceAccountTemplate
template to make note of that, and adds a new template string to use,ServiceAccountCredentialsTemplate
.Alternatively we could just update the
ServiceAccountTemplate
instead of addingServiceAccountCredentialsTemplate
, however, I felt this was a cleaner and more explicit path forward.See also: hashicorp/vault-plugin-auth-gcp#108
Note: The changes to
go.sum
reflect ago mod tidy
operation; I get the same changes if I run that on themaster
branch