feat: Airbyte snapshot pull + seed-from-snapshot workflow#30
Closed
feat: Airbyte snapshot pull + seed-from-snapshot workflow#30
Conversation
zozo123
added a commit
that referenced
this pull request
Feb 23, 2026
Resolve conflicts between the snapshot and fixture features: - --snapshot flag seeds from a snapshot profile - --fixture flag resolves fixtures from service fixtures/ dir - Mutual exclusion: only one of --snapshot, --fixture, or file path Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
10 tasks
Contributor
Author
|
Superseded by #33 (consolidated PR) |
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.
Summary
This PR adds an end-to-end snapshot ingestion path in one place:
doubleagent snapshotcommand family:pull,list,inspect,deleteservice.yaml(connectorblock) with Airbyte supportservices/_lib/snapshot_pull/pyairbytebackendmanifest.json,seed.json, per-resource JSON)doubleagent seed <service> --snapshot <profile>~/.doubleagent/snapshots/<service>/<profile>/seed.jsonRationale
Single PR is intentional here because these parts are tightly coupled and only provide user value together:
snapshot pullwithout seed integration leaves a dead-end artifact flow.seed --snapshotwithout connector pull has no built-in source of truth.This keeps the model simple:
Airbyte pull -> local snapshot profile -> existing /_doubleagent/seed pathNo new runtime state model, no namespace/COW/bootstrap mechanics, and no change to the required service interface.
Behavior notes
connector.required_env).--no-redactis explicit.DOUBLEAGENT_COMPLIANCE_MODE=strict) blocks snapshot pulls.pyairbyteonly.Validation
cargo fmtcargo checkcargo test -p doubleagent-corecargo test -p doubleagentcargo run -p doubleagent -- snapshot --helpcargo run -p doubleagent -- seed --helppython3 -m snapshot_pull --help(fromservices/_lib)