Closed amkoehler closed 2 years ago
When we use this sample code to upload a file we are facing the issue that singedurl is not generating with the upload key.
when we try 3 or 4 times the same code is generating the correct upload key with singedurl however its failing for 8 out of 10 times
@augustogoncalves
Hi, any updates on whether the ObjectsApi's methods getObjects() and uploadObject(), be internally updated and those using forge-apis npm package won't have to modify their code? This is with respect to the deprecation mail that was sent out in favor of a new set of Data Management API endpoints to allow direct upload and download from the underlying AWS S3 bucket.
Hello - recently it was announced that certain data management API calls would be deprecated in favor of direct uploads and downloads from the underlying AWS S3 bucket. We make use of a couple of methods in the
ObjectsApi
and I'm wondering if we'll need to plan for these changes or if this package will be handling that automatically.For example, we use
ObjectsApi.uploadChunk
for resumable uploads, which calls this soon-to-be-deprecated method. WilluploadChunk
be updated under the hood to call the new direct-to-s3 endpoint?
v0.9.1 implements the wrapper for directs3. it also introduces 2 generic methods to hide the complexity of using s3. They are called downloadResources() and uploadResources(), see samples/dmSample2.js and dmSample-complex.js for examples.
Hey @cyrillef - I'm only a year late on responding! We're still on v0.8.4 but looks like upgrading to 0.9.x will resolve this as you said. I like the convenience of uploadResources
, but if we're already using uploadChunk
is there a compelling reason to migrate to `uploadResources?
Hi, no reason to move to this function if you already using chunks.
Thanks @cyrillef. This has me a little confused on the deprecation. Under the hood, uploadChunks
calls a deprecated endpoint:
I opened #106 for a separate issue with uploadResources
, so for now we're still on uploadChunks
. Is there truly no reason to move if uploadChunks
is calling a deprecated endpoint?
Hello - recently it was announced that certain data management API calls would be deprecated in favor of direct uploads and downloads from the underlying AWS S3 bucket. We make use of a couple of methods in the
ObjectsApi
and I'm wondering if we'll need to plan for these changes or if this package will be handling that automatically.For example, we use
ObjectsApi.uploadChunk
for resumable uploads, which calls this soon-to-be-deprecated method. WilluploadChunk
be updated under the hood to call the new direct-to-s3 endpoint?