feat: bulk CSV background jobs setup#6448
Open
matzduniuk wants to merge 63 commits into
Open
Conversation
✅ Deploy Preview for partners-bloom-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-angelopolis canceled.
|
✅ Deploy Preview for bloom-public-seeds ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-exygy-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
YazeedLoonat
requested changes
Jul 9, 2026
YazeedLoonat
left a comment
Collaborator
There was a problem hiding this comment.
looks good but a few tweaks
ludtkemorgan
reviewed
Jul 9, 2026
…oom-housing/bloom into 6384/bulk-csv-background-jobs
662c527 to
f648465
Compare
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
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.
This PR addresses #6384
Description
How Can This Be Tested/Reviewed?
Re-set up the backend application to apply new migrations.
Using Postman, perform the following operations:
2a. Create a new background job using the POST /jobs endpoint, providing a valid listingId (copy one from Prisma Studio → listing table) and any string value for inputS3Key. The response should return a BackgroundJob object with status: "processing".
2b. Using the same listingId, attempt to create a second job using the POST /jobs endpoint again — this should return a 409 Conflict error, confirming that duplicate active jobs for the same listing are blocked.
2c. Using the listingId from step 3a, retrieve the currently active job using the GET /jobs?listingId= endpoint. The response should return the same job object created in 3a.
2d. Copy the id field from the response in 3a and retrieve the job directly using the GET /jobs/ endpoint. Confirm the returned object matches.
Tip
The above steps should also be performed using invalid data — missing or malformed body fields on POST, a non-> UUID listingId, an unrecognised job ID on the GET by ID endpoint, and requests with the passkey or Authorization > > header omitted — to verify proper error and validation handling.
Author Checklist:
yarn generate:clientand/or created a migration when requiredReview Process: