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
@then('after a wait of {duration}, at least {lower_bound:d} and at most {upper_bound:d} flowfiles are produced and placed in the "{directory}" directory')
177
+
@then('after a wait of {duration}, at least {lower_bound:d} and at most {upper_bound:d} files are produced and placed in the "{directory}" directory')
Copy file name to clipboardExpand all lines: extensions/aws/tests/features/s3.feature
+11-11Lines changed: 11 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
33
33
34
34
When both instances start up
35
35
36
-
Then there is a single file with "LH_O#L|FD<FASD{FO#@$#$%^ \"#\"$L%:\"@#$L\":test_data#$#%#$%?{\"F{"content in the "/tmp/output" directory in less than 20 seconds
36
+
Then a single file with the content "LH_O#L|FD<FASD{FO#@$#$%^ \"#\"$L%:\"@#$L\":test_data#$#%#$%?{\"F{"is placed in the "/tmp/output" directory in less than 20 seconds
37
37
And the object on the s3 server is "LH_O#L|FD<FASD{FO#@$#$%^ \"#\"$L%:\"@#$L\":test_data#$#%#$%?{\"F{"
38
38
And the object content type on the s3 server is "application/octet-stream" and the object metadata matches use metadata
39
39
And the Minifi logs contain the following message: "in a single upload" in less than 10 seconds
@@ -58,7 +58,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
58
58
And the http proxy server is set up
59
59
When all instances start up
60
60
61
-
Then there is a single file with "LH_O#L|FD<FASD{FO#@$#$%^ \"#\"$L%:\"@#$L\":test_data#$#%#$%?{\"F{"content in the "/tmp/output" directory in less than 20 seconds
61
+
Then a single file with the content "LH_O#L|FD<FASD{FO#@$#$%^ \"#\"$L%:\"@#$L\":test_data#$#%#$%?{\"F{"is placed in the "/tmp/output" directory in less than 20 seconds
62
62
And the object on the s3 server is "LH_O#L|FD<FASD{FO#@$#$%^ \"#\"$L%:\"@#$L\":test_data#$#%#$%?{\"F{"
63
63
And the object content type on the s3 server is "application/octet-stream" and the object metadata matches use metadata
64
64
And no errors were generated on the http-proxy regarding "http://s3-server-s3-1:9090/test_bucket/test_object_key"
@@ -81,7 +81,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
81
81
82
82
When both instances start up
83
83
84
-
Then there is a single file with "LH_O#L|FD<FASD{FO#@$#$%^ \"#\"$L%:\"@#$L\":test_data#$#%#$%?{\"F{"content in the "/tmp/output" directory in less than 20 seconds
84
+
Then a single file with the content "LH_O#L|FD<FASD{FO#@$#$%^ \"#\"$L%:\"@#$L\":test_data#$#%#$%?{\"F{"is placed in the "/tmp/output" directory in less than 20 seconds
85
85
And the object bucket on the s3 server is empty in less than 10 seconds
86
86
87
87
Scenario: Deletion of a non-existent s3 object succeeds
@@ -96,7 +96,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
96
96
97
97
When both instances start up
98
98
99
-
Then there is a single file with "test"content in the "/tmp/output" directory in less than 20 seconds
99
+
Then a single file with the content "test"is placed in the "/tmp/output" directory in less than 20 seconds
100
100
And the object bucket on the s3 server is empty in less than 10 seconds
101
101
102
102
Scenario: Deletion of a s3 object through a proxy-server succeeds
@@ -124,7 +124,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
124
124
125
125
When all instances start up
126
126
127
-
Then there is a single file with "LH_O#L|FD<FASD{FO#@$#$%^ \"#\"$L%:\"@#$L\":test_data#$#%#$%?{\"F{"content in the "/tmp/output" directory in less than 20 seconds
127
+
Then a single file with the content "LH_O#L|FD<FASD{FO#@$#$%^ \"#\"$L%:\"@#$L\":test_data#$#%#$%?{\"F{"is placed in the "/tmp/output" directory in less than 20 seconds
128
128
And the object bucket on the s3 server is empty in less than 10 seconds
129
129
And no errors were generated on the http-proxy regarding "http://s3-server-s3-4:9090/test_bucket/test_object_key"
130
130
@@ -149,7 +149,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
149
149
150
150
When all instances start up
151
151
152
-
Then there is a single file with "test"content in the "/tmp/output" directory in less than 20 seconds
152
+
Then a single file with the content "test"is placed in the "/tmp/output" directory in less than 20 seconds
153
153
154
154
Scenario: A MiNiFi instance can download s3 bucket objects via a http-proxy
155
155
Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
@@ -176,7 +176,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
176
176
177
177
When all instances start up
178
178
179
-
Then there is a single file with "test"content in the "/tmp/output" directory in less than 20 seconds
179
+
Then a single file with the content "test"is placed in the "/tmp/output" directory in less than 20 seconds
180
180
And no errors were generated on the http-proxy regarding "http://s3-server-s3-6:9090/test_bucket/test_object_key"
181
181
182
182
Scenario: A MiNiFi instance can list an S3 bucket directly
@@ -197,7 +197,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
197
197
198
198
When all instances start up
199
199
200
-
Then there are 2 files in the "/tmp/output" directory in less than 20 seconds
200
+
Then 2 files are placed in the "/tmp/output" directory in less than 20 seconds
201
201
202
202
Scenario: A MiNiFi instance can list an S3 bucket objects via a http-proxy
203
203
Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
@@ -220,7 +220,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
220
220
221
221
When all instances start up
222
222
223
-
Then there is 1 file in the "/tmp/output" directory in less than 20 seconds
223
+
Then 1 file is placed in the "/tmp/output" directory in less than 20 seconds
224
224
And no errors were generated on the http-proxy regarding "http://s3-server-s3-8:9090/test_bucket"
225
225
226
226
Scenario: A MiNiFi instance transfers data in multiple parts to s3
@@ -236,7 +236,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
236
236
237
237
When all instances start up
238
238
239
-
Then there is 1 file in the "/tmp/output" directory in less than 20 seconds
239
+
Then 1 file is placed in the "/tmp/output" directory in less than 20 seconds
240
240
And the object on the s3 server is present and matches the original hash
241
241
And the Minifi logs contain the following message: "passes the multipart threshold, uploading it in multiple parts" in less than 10 seconds
242
242
@@ -260,7 +260,7 @@ Feature: Sending data from MiNiFi-C++ to an AWS server
260
260
And the http proxy server is set up
261
261
When all instances start up
262
262
263
-
Then there is 1 file in the "/tmp/output" directory in less than 20 seconds
263
+
Then 1 file is placed in the "/tmp/output" directory in less than 20 seconds
264
264
And the object on the s3 server is present and matches the original hash
265
265
And the Minifi logs contain the following message: "passes the multipart threshold, uploading it in multiple parts" in less than 10 seconds
266
266
And no errors were generated on the http-proxy regarding "http://s3-server-s3-10:9090/test_bucket/test_object_key"
0 commit comments