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

Update legacy actions used for C2PA injection #79

Open
1 task
benhylau opened this issue Mar 31, 2022 · 1 comment
Open
1 task

Update legacy actions used for C2PA injection #79

benhylau opened this issue Mar 31, 2022 · 1 comment
Assignees

Comments

@benhylau
Copy link
Contributor

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:

./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

  • ...
@anaulin
Copy link
Contributor

anaulin commented Mar 31, 2022

./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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants