Current implementation assume we are always proxying a /{file} operation, but its useful to proxy the whole s3 API sometimes, including support of ListObject which is issued against the bucket resource URL.
Current implementation ends up forwarding {file} in this case because the file param is not substituted in the router.
This PR enables bucket level operations, which in general are dangerous, thus is it is an opt-in flag
Current implementation assume we are always proxying a /{file} operation, but its useful to proxy the whole s3 API sometimes, including support of ListObject which is issued against the bucket resource URL. Current implementation ends up forwarding
{file}
in this case because the file param is not substituted in the router. This PR enables bucket level operations, which in general are dangerous, thus is it is an opt-in flag