Review the api env, db schema, and cron jobs to find out what needs to be updated to have the api use pickup to handle pinning service requests.
TODO
note: the env var CLUSTER_SERVICE takes precedence over CLUSTER_API_URL, so we can add a value for CLUSTER_API_URL whenever we like, and then delete the CLUSTER_SERVICE env var when we are ready for to make the switch.
Parent: web3-storage/pickup#68
Review the api env, db schema, and cron jobs to find out what needs to be updated to have the api use pickup to handle pinning service requests.
TODO
api/src/routes/pins-add.jsto specify ElasticIpfs as the service when calling createUploadapi/src/routes/pins-replace.jsto specify ElasticIpfs as the service when calling createUploadcron/src/bin/pins.jsto add a cluster client configured to hitpickup.cron/src/jobs/pins.jsto addElasticIpfsto the list of Clusters to checkcron/src/bin/pins.jsto add a check pin statuses on pickup for via status.allstagingworker env var forCLUSTER_API_URLset to staging pickup urlstagingworker env var forCLUSTER_SERVICEprodworker env var forCLUSTER_API_URLset to prod pickup urlprodworker env var forCLUSTER_SERVICEnote: the env var
CLUSTER_SERVICEtakes precedence overCLUSTER_API_URL, so we can add a value forCLUSTER_API_URLwhenever we like, and then delete theCLUSTER_SERVICEenv var when we are ready for to make the switch.Parent: web3-storage/pickup#68