tangled.org
Ingest sh.tangled.repo records off the jetstream. This enables third-party clients to create tangled.sh git repositories on a user's PDS and tangled to pick up the record and create the repo on the knot, and in the appview db.
Monorepo for Tangled
tangled.org
ingester: ingest sh.tangled.repo records from jetstream #112
closed
opened by
rockorager.dev
targeting
master
expand 2 commits
hide 2 commits
438af2b5
appview: repo: move repo validation to db package
4fd6be3c
ingester: ingest sh.tangled.repo records from jetstream
Ingest sh.tangled.repo records off the jetstream. This enables
third-party clients to create tangled.sh git repositories on a user's
PDS and tangled to pick up the record and create the repo on the knot,
and in the appview db.
Also my diff has several gofumpt changes...I can change to regular go fmt if that's what y'all are using
Is there a way to test this without being in production? A mock jetstream?
After 2 minutes of thought, I realize that given the hostile nature of the jetstream this really ought to be heavily unit tested to ensure tangled only ingests valid data.
I wonder if before adding more ingester methods it makes sense to put together a test harness for data off the jetstream. Would need mock data (fuzzing would be great here), mock db, and mock knot client.
oppi.li
theres a bit of nuance here, that we are yet to figure out, but it would probably be best to ingest repos once we deprecate knot secrets (we are working towards this by using service-auth).
closed without merging
Note: I have not tested this. Is there a way to test this without being in production? A mock jetstream?