You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When files land in the auto ingest bucket we get a notification to our api, we then pick up these assets and bring them into our platform and begin to process them as fast as we can. This allows users to drop large amounts of assets on us in a fire-and-forget fashion, either sent from their own system or manually using tools like cyberduck.
All we need is an api notification once the file finishes being written to Storj so we can go and fetch it. Other notification for other actions (delete, replace etc) are helpful but nowhere near as important.
Description:
When files land in the auto ingest bucket we get a notification to our api, we then pick up these assets and bring them into our platform and begin to process them as fast as we can. This allows users to drop large amounts of assets on us in a fire-and-forget fashion, either sent from their own system or manually using tools like cyberduck.
All we need is an api notification once the file finishes being written to Storj so we can go and fetch it. Other notification for other actions (delete, replace etc) are helpful but nowhere near as important.
What is the problem/pain point?
What is the impact?
Why now?
Links:
The text was updated successfully, but these errors were encountered: