You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
streams + attachment size check + attachment url in body (#72)
* Created new `Read file` action instead of existing due to incorrect output metadata, old one set as deprecated
* Fix memory leak for `Read file` action and `Get New and Updated S3 Objects` trigger, also added attachment url in message body to them
* Default value for environment variable `ATTACHMENT_MAX_SIZE` increased from `10000000` (almost **10** MB) to `104857600` bytes (**100** MB)
* Implemented additional check attachments size in `Get New and Updated S3 Objects` trigger
* Get rid of vulnerabilities in dependencies
|`ATTACHMENT_MAX_SIZE`| false | For `elastic.io` attachments configuration. Maximal possible attachment size in bytes. By default set to 1000000 and according to platform limitations CAN'T be bigger than that. | Up to `1000000` bytes|
50
+
|`ATTACHMENT_MAX_SIZE`| false | For `elastic.io` attachments configuration. Maximal possible attachment size in bytes. By default set to `104857600` and according to platform limitations **CAN'T** be bigger than that. | Up to `104857600` bytes (100MB)|
51
51
|`ACCESS_KEY_ID`| false | For integration-tests is required to specify this variable ||
52
52
|`ACCESS_KEY_SECRET`| false | For integration-tests is required to specify this variable ||
53
53
|`REGION`| false | For integration-tests is required to specify this variable ||
@@ -72,18 +72,27 @@ Triggers to get all new and updated s3 objects since last polling.
72
72
73
73
#### List of Expected Config fields
74
74
-**Bucket Name and folder** - name of S3 bucket to read files from
75
-
-**Emit Behaviour**: Options are: default is `Emit Individually` emits each object in separate message, `Fetch All` emits all objects in one message
75
+
-**Emit Behaviour**: Options are: default is `Emit Individually` emits each object in separate message, `Fetch All` emits all objects as array in one object with key `results`
76
76
-**Start Time**: Start datetime of polling. Default min date:`-271821-04-20T00:00:00.000Z`
77
77
-**End Time**: End datetime of polling. Default max date: `+275760-09-13T00:00:00.000Z`
78
-
-**Enable File Attachments**: If selected, the contents of the file will be exported in addition to the file metadata.
78
+
-**Enable File Attachments**: If selected, the contents of the file will be exported in addition to the attachment.
79
+
79
80
80
81
<details>
81
82
<summary>Output metadata</summary>
82
83
84
+
If **Emit Behaviour** selected as `Emit Individually` - emits each object in separate message with schema below, if `Fetch All` emits all objects as array in one object with key `results`, each item regards schema below
85
+
86
+
`attachmentUrl` appears only if selected **Enable File Attachments**
87
+
83
88
```json
84
89
{
85
90
"type": "object",
86
91
"properties": {
92
+
"attachmentUrl": {
93
+
"type": "string",
94
+
"required": true
95
+
},
87
96
"Key": {
88
97
"type": "string",
89
98
"required": true
@@ -181,6 +190,14 @@ File type resolves by it's extension. The name of attachment would be same to fi
0 commit comments