-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Rename repo? Decouple repo? this is not upload-api #50
Comments
This was referenced Nov 29, 2022
Closed
Closed
Merged
vasco-santos
added a commit
that referenced
this issue
Dec 1, 2022
Adds replicator stack by moving its content out of CARPARK on the direction to #50 Implementation details: - replicator-stack has 2 queues, one to replicate CARs and other to replicate .idx files. At first I was attempting to do both in one single queue. Ended up moving to 2 queues because I would need to have handlers to identify origin bucket and have a hardcoded mapping where I would see if it was carpark/satnav and with that select the appropriate CF destination bucket. - while my decision for 2 queues was based on the above, it might actually be the best approach to not have queues throttling flow on copies from independent buckets. - also important noticing that despite 2 queues, there is only one handler function code. The lambda code is the same, but it is injected with destination BUCKET_NAME according to the queue it is handling. Closes #54 Co-authored-by: Oli Evans <oli@protocol.ai>
wait this isn't the upload-api? |
We sat together and decided to move this way Today
Tomorrow
|
This was referenced Dec 9, 2022
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
The text was updated successfully, but these errors were encountered: