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
📅 Due date: N/A
🎯 Success criteria: Update legacy actions to support new internal file actions defined by configuration.
Our file watcher now watches for ./{collection_id}/input/*.zip. A collection folder with 3 actions defined in config looks like:
./collection_id/
input/*.zip (watched)
action-archive/ (the action handles this)
action-create/
action-store/
This breaks legacy actions (create, add, update, store, custom). The way it'll work for the legacy actions is:
./create gets replaced with a collection_id so we watch, for example, ./capture-app-collection/input/*.zip
./store gets replaced with a collection_id so we watch, for example, ./ipfs-store-collection/input/*.zip
We will no longer handle raw JPGs as input. The only format coming in should be ZIPs.
The HTTP handler will need to output conformant ZIPs in the create endpoint. Similarly, we need a new way of accepting JPG files that are currently received via FTP folder drops.
To Do
...
The text was updated successfully, but these errors were encountered:
./create gets replaced with a collection_id so we watch, for example, ./capture-app-collection/input/*.zip
Reminder that at the moment create is not watched at all, but instead handled via an HTTP endpoint that uses all the "legacy" non-collection-specific directory paths. If create becomes collection-specific, there will have to be some way for the HTTP request to provide the collection_id (could be in the request body, could be part of the JWT metadata, or something else).
Task Summary
📅 Due date: N/A
🎯 Success criteria: Update legacy actions to support new internal file actions defined by configuration.
Our file watcher now watches for
./{collection_id}/input/*.zip
. A collection folder with 3 actions defined in config looks like:This breaks legacy actions (create, add, update, store, custom). The way it'll work for the legacy actions is:
./create
gets replaced with acollection_id
so we watch, for example,./capture-app-collection/input/*.zip
./store
gets replaced with acollection_id
so we watch, for example,./ipfs-store-collection/input/*.zip
We will no longer handle raw JPGs as input. The only format coming in should be ZIPs.
The HTTP handler will need to output conformant ZIPs in the
create
endpoint. Similarly, we need a new way of accepting JPG files that are currently received via FTP folder drops.To Do
The text was updated successfully, but these errors were encountered: