Build and deploy both pilot binaries in the Cloud Build pipeline - #153
Merged
Merged
Conversation
cloudbuild.yaml now builds trace-commons-upload-claim-issuer alongside trace-commons-ingest (the issuer holds the per-user subject + /v1/enroll handlers; deploying only ingest silently skips issuer-side changes). pull-and-install.sh deploys both by default (issuer first so its JWKS is up before ingest re-fetches it), with per-binary ingest/issuer overrides. Validated: one Cloud Build run publishes both binaries + latest pointers. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Why
The pilot runs two services —
trace-commons-ingestandtrace-commons-upload-claim-issuer— and changes land in either. The issuer holds the device-key upload-claim logic, the per-usersubjectderivation (#152), and the/v1/enrollhandler (#150). The original pipeline built/deployed only ingest, so an issuer-side change deploys silently as a no-op (this bit the #152 deploy — the per-user subject didn't go live until the issuer was built separately).What
cloudbuild.yamlnow builds both binaries in one run (ingest with the cloud features; the issuer without — it doesn't use GCS/KMS/NEAR-AI), publishing each togs://tc-pilot-artifacts-20260518/binaries/<bin>/<tag>/with its ownlatest.txt. The secondcargo buildreuses the first's compiled deps, so the marginal cost is small.deploy/pilot-gcp/pull-and-install.shdeploys both by default (issuer first so its JWKS is up before ingest restarts and re-fetches it), each sha-verified with backup + rollback.ingest/issuerargs deploy just one.Validated
One Cloud Build run (
E2_HIGHCPU_32, ~6.5 min) built both binaries and updated bothlatest.txtpointers.