Conversation
10b57be to
3094514
Compare
|
please review. |
|
I think adding an assertion for the case where this is enabled on versions before 33 makes sense. |
Added! Thanks. |
Ma27
left a comment
There was a problem hiding this comment.
@provokateurin how hard would it be to extend the VM test to make sure it's properly serving pre-signed files? I imagine you'd have to upload a file and obtain a download link?
If it's reasonably doable, I'd really like to see test-coveratge for it.
the verification procedure is described here: |
Should be easy, the link is just a WebDAV prop that can be queried. |
|
Despite of installing a patched version of Nextcloud with this PR and enabling the presigned urls, I am unable to see them, unfortunately. I am getting empty values: |
|
Anything interesting in the error logs? |
No, nothing special. I set the loglevel to 0 to be sure, but there is nothing suspicious, the request is served normally, the file is found correctly. |
|
I have installed a Nextcloud docker and I get the same issue, so it's not related to the NixOS packaging. I am investigating it further for a likely Nextcloud bug. |
|
I filed nextcloud/server#59249 but it does not seem to a prority for the nextcloud S3 team |
|
The bug was fixed today, I assume it will be fixed in version 35 of nextcloud. Edit: Oh no, it is backported to 33 and 34! I will run tests soon to confirm if it works. @provokateurin it would be cool if you could review it to backport |
| 'use_ssl' => ${lib.boolToString s3.useSsl}, | ||
| ${lib.optionalString (s3.region != null) "'region' => '${s3.region}',"} | ||
| 'use_path_style' => ${lib.boolToString s3.usePathStyle}, | ||
| 'use_presigned_url' => ${lib.boolToString s3.usePresignedUrl}, |
There was a problem hiding this comment.
revisiting this, what was the reason we're not setting this settings?
There was a problem hiding this comment.
It's a new nextcloud feature. I mean, it will be when it starts working.
There was a problem hiding this comment.
Can you elaborate? I don't follow how this relates to my question, sorry.
There was a problem hiding this comment.
It seems that I do not understand your question, then.
There was a problem hiding this comment.
@Ma27 Are you asking why not just set use_presigned_url via settings instead of adding a new option?
|
No rush guys, this one liner is being deliberated for only 171 days. We have plenty of time to take a really good decision which analyses full spectrum of potential effects in micro- and macro- scale. |
|
Fine, making a decision then. It's Won't do. We've been literally waiting for you to answer and you come with sarcasm about things not moving? 🤡 |
This PR extends S3 configuration with a
use_presigned_urlintroduced in Nextcloud 33 with nextcloud/server#54436Things done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.