feat(canopy): bump bestool-canopy 0.7.0 / kopia 0.4.0 and thread run_id through restore runs#94
Merged
Conversation
0.7.0 marks every generated schema struct #[non_exhaustive] with a bon-derived builder, so switch the IntentDescriptor / BTreeMapValue / RestoreCapabilitiesArgs / RestoreCredentialsArgs / VerificationArgs construction sites from struct literals to builders. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Source-compatible; the proxy API pgro uses is unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Canopy asks each restore run to carry a client-minted run-uuid on its credential requests and its verification report so it can correlate them; the field is optional today but will be enforced. Mint a run_id when a canopy-backed restore Job is created, persist it on the restore status, and thread it to the run's credential requests (via a PGRO_RUN_ID sidecar env forwarded through the broker, whose creds cache is now keyed by run_id) and to the verification report. Non-run credential fetches deliberately carry no run_id: the reconcile-time repo-password poll and the snapshot-list job are not restore runs, and minting throwaway uuids would create phantom runs. 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.
🤖 Updates the bestool crates and threads a canopy run-uuid through restore runs.
Dependency bumps
bestool-canopy0.6.1 → 0.7.0. 0.7.0 marks every generated schema struct#[non_exhaustive]with abon-derived builder, so theIntentDescriptor/BTreeMapValue/RestoreCapabilitiesArgs/RestoreCredentialsArgs/VerificationArgsconstruction sites move from struct literals to builders.bestool-kopia0.3.4 → 0.4.0. Source-compatible; the proxy API is unchanged.run_id threading
Canopy asks each restore run to carry a client-minted run-uuid on its credential requests and its verification report so it can correlate them. The field is optional today but is documented as becoming mandatory.
run_idwhen a canopy-backed restore Job is created and persist it onPostgresPhysicalRestoreStatus.runId.PGRO_RUN_IDsidecar env, forwarded through the broker — whose creds cache is now keyed byrun_id, so within-run STS refreshes still hit cache while each run gets its own attributed credentials.Non-run credential fetches deliberately carry no
run_id: the reconcile-time repo-password poll and the snapshot-list job are not restore runs, and minting throwaway uuids would create phantom runs in canopy. If canopy later requires a run_id on read-only credential fetches, that is a follow-up.Regenerated
crds.yamlfor the new status field and updated the README status table.