4 commits

Author	SHA1	Message	Date
Iván Ovejero	0847623f85	feat(core): Switch binary filesystem mode to nested path structure (#7307) ... Depends on #7253 | Story: [PAY-863](https://linear.app/n8n/issue/PAY-863/switch-binary-filesystem-mode-to-nested-path-structure) This PR introduces `filesystem-v2` to store binary data in the filesystem in the same format as `s3`.	2023-10-10 10:06:06 +02:00
Iván Ovejero	1a661e6d00	feat(core): Integrate object store as binary data manager (#7253) ... Depends on: #7225 | Story: [PAY-848](https://linear.app/n8n/issue/PAY-848) This PR integrates the object store service as a new binary data manager for Enterprise.	2023-10-05 15:25:17 +02:00
Iván Ovejero	1691223789	fix(core): Account for itemless case on restoring binary data ID (#7305) ... https://linear.app/n8n/issue/PAY-862	2023-10-02 09:13:55 +02:00
Iván Ovejero	33991e92d0	fix(core): Fix missing execution ID in webhook-based workflow producing binary data (#7244) ... Story: https://linear.app/n8n/issue/PAY-839 This is a longstanding bug, fixed now so that the S3 backend for binary data can use execution IDs as part of the filename. To reproduce: 1. Set up a workflow with a POST Webhook node that accepts binary data. 2. Activate the workflow and call it sending a binary file, e.g. `curl -X POST -F "file=@/path/to/binary/file/test.jpg" http://localhost:5678/webhook/uuid` 3. Check `~/.n8n/binaryData`. The binary data and metadata files will be missing the execution ID, e.g. `11869055-83c4-4493-876a-9092c4708b9b` instead of `39011869055-83c4-4493-876a-9092c4708b9b`.	2023-09-25 12:30:28 +02:00