-
Notifications
You must be signed in to change notification settings - Fork 119
Open
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps uppi/psa-follow-uptopic/potIssues handled by PT.Issues handled by PT.topic/psa
Description
Overarching user needs / context:
- When migrating pinning to Elastic Provider (pick-up service), we will need the existing pinned pins to be on S3 so the Elastic Provider can provide them.
- Also, we need to make sure they are stored in 2 systems rather than 1, so we will still be able to retrieve pinned files from IPFS once we migrate the PSA to use picup.
Scope of this ticket:
- A backup job that copies existing pins that are marked as pinned to S3. It should be written in a way that it can be run repeatedly from cron, to keep backing up pinned pins.
Acceptance criteria:
- All pinned pins, processed through PSA to cluster should appear in S3
- The script/job can be run multiple times
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps uppi/psa-follow-uptopic/potIssues handled by PT.Issues handled by PT.topic/psa