Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Eventing / Event Notifications #103

Closed
iglesiasbrandon opened this issue Jul 31, 2024 · 1 comment
Closed

Eventing / Event Notifications #103

iglesiasbrandon opened this issue Jul 31, 2024 · 1 comment

Comments

@iglesiasbrandon
Copy link
Collaborator

iglesiasbrandon commented Jul 31, 2024

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:

@iglesiasbrandon
Copy link
Collaborator Author

duplicate of #87

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Archive
Development

No branches or pull requests

1 participant