it must be possible to add custom params to presignURL about helix-universal HOT 3 CLOSED

@trieloff it seems that the presigned urls are somewhat limited when we want to add custom metadata.
problem problem is, that the metadata need to be included in the signing step (key + value), but the value can later not be changed :-(

e.g. when we want to store the source location in a x-amz-meta-x-source-location metadata, we would need to know the source location value before hand. i.e. the pre-signer already needs to resolve it.

I think for source location is is ok, but maybe for others it isn't.

alternatively, we give the content providers (word2md, data-embed, gdocs2md) write access roles to the content-bus.

from helix-universal.

e.g. when we want to store the source location in a x-amz-meta-x-source-location metadata, we would need to know the source location value before hand. i.e. the pre-signer already needs to resolve it.
I think for source location is is ok, but maybe for others it isn't.

Yes, e.g. for x-amz-meta-last-modified which the caller can't know beforehand

from helix-universal.

🎉 This issue has been resolved in version 1.6.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from helix-universal.