-
Notifications
You must be signed in to change notification settings - Fork 2
feat(tmproto): typed per-provider credentials for ServiceAccountAccess #477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sujanchalla0510
wants to merge
1
commit into
adcontextprotocol:main
Choose a base branch
from
sujanchalla0510:feat/tmproto-typed-service-account-credentials
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Medium: Round-trip fidelity regression for real GCP credentials. A production GCP service-account key JSON carries
type,private_key_id,client_id,auth_uri,auth_provider_x509_cert_url,client_x509_cert_url,universe_domain— none modeled here.decodeServiceAccountCredentialsat L346 does a plainjson.Unmarshalinto this 4-field struct, so every unmodeled field is silently dropped on decode and gone on re-marshal. The priormap[string]anyround-tripped a full SA JSON losslessly; the new typed path does not. Note the asymmetry: unknown providers preserve everything viaRawServiceAccountCredentials.Fields, butgcp/aws— the providers you do type — lose data. The four modeled fields are enough to mint a JWT assertion, so auth still works; the loss istype/private_key_id/cert URLs, which some consumers (google.CredentialsFromJSONrequirestype) need. Recommend an overflow-capture field to preserve unmodeled keys, or document the contract as deliberately lossy. The round-trip tests only feed exactly-modeled fields, so they can't catch this.