files.com 1.1.641 → 1.1.642
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/_VERSION +1 -1
- data/docs/sync.md +10 -2
- data/lib/files.com/models/sync.rb +12 -0
- data/lib/files.com/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: ae221e1554e5194299d577bc71a497aa8f80cb790a0eb54c33aef44adcde76db
|
|
4
|
+
data.tar.gz: 9febc3638c79d6d415527049c6d8462d97dd0d8b8cd5638f06aed113337e0004
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 660cc67b383441d2c8b91d057c197d4b67de7a1786f803a322f48ac960dab908562e5584e2bcb047ca04f915fc61cba393fc008922e07f4d98c0bcaec3504f81
|
|
7
|
+
data.tar.gz: b56abafc82b321f0900a73d4772d0c99ba77b9eeb0302e292bcb44d1f39adbb20b04f7c8d51abe9a809c8a737d5f0457ebe64b1ebbc610b561973cb0a8c4c6d7
|
data/_VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
1.1.
|
|
1
|
+
1.1.642
|
data/docs/sync.md
CHANGED
|
@@ -22,6 +22,7 @@
|
|
|
22
22
|
"disabled": true,
|
|
23
23
|
"trigger": "example",
|
|
24
24
|
"trigger_file": "example",
|
|
25
|
+
"always_write_trigger_file": true,
|
|
25
26
|
"include_patterns": [
|
|
26
27
|
"example"
|
|
27
28
|
],
|
|
@@ -102,6 +103,7 @@
|
|
|
102
103
|
* `disabled` (boolean): Is this sync disabled?
|
|
103
104
|
* `trigger` (string): Trigger type: daily, custom_schedule, or manual
|
|
104
105
|
* `trigger_file` (string): Some MFT services request an empty file (known as a trigger file) to signal the sync is complete and they can begin further processing. If trigger_file is set, a zero-byte file will be sent at the end of the sync.
|
|
106
|
+
* `always_write_trigger_file` (boolean): If true, the trigger file will be sent at the end of a successful sync even when no files were transferred.
|
|
105
107
|
* `include_patterns` (array(string)): Array of glob patterns to include
|
|
106
108
|
* `exclude_patterns` (array(string)): Array of glob patterns to exclude
|
|
107
109
|
* `created_at` (date-time): When this sync was created
|
|
@@ -171,6 +173,7 @@ Files::Sync.create(
|
|
|
171
173
|
sync_interval_minutes: 1,
|
|
172
174
|
trigger: "example",
|
|
173
175
|
trigger_file: "example",
|
|
176
|
+
always_write_trigger_file: true,
|
|
174
177
|
workspace_id: 1
|
|
175
178
|
)
|
|
176
179
|
```
|
|
@@ -197,6 +200,7 @@ Files::Sync.create(
|
|
|
197
200
|
* `sync_interval_minutes` (int64): Frequency in minutes between syncs. If set, this value must be greater than or equal to the `remote_sync_interval` value for the site's plan. If left blank, the plan's `remote_sync_interval` will be used. This setting is only used if `trigger` is empty.
|
|
198
201
|
* `trigger` (string): Trigger type: daily, custom_schedule, or manual
|
|
199
202
|
* `trigger_file` (string): Some MFT services request an empty file (known as a trigger file) to signal the sync is complete and they can begin further processing. If trigger_file is set, a zero-byte file will be sent at the end of the sync.
|
|
203
|
+
* `always_write_trigger_file` (boolean): If true, the trigger file will be sent at the end of a successful sync even when no files were transferred.
|
|
200
204
|
* `workspace_id` (int64): Workspace ID this sync belongs to
|
|
201
205
|
|
|
202
206
|
|
|
@@ -251,7 +255,8 @@ Files::Sync.update(id,
|
|
|
251
255
|
src_remote_server_id: 1,
|
|
252
256
|
sync_interval_minutes: 1,
|
|
253
257
|
trigger: "example",
|
|
254
|
-
trigger_file: "example"
|
|
258
|
+
trigger_file: "example",
|
|
259
|
+
always_write_trigger_file: true
|
|
255
260
|
)
|
|
256
261
|
```
|
|
257
262
|
|
|
@@ -278,6 +283,7 @@ Files::Sync.update(id,
|
|
|
278
283
|
* `sync_interval_minutes` (int64): Frequency in minutes between syncs. If set, this value must be greater than or equal to the `remote_sync_interval` value for the site's plan. If left blank, the plan's `remote_sync_interval` will be used. This setting is only used if `trigger` is empty.
|
|
279
284
|
* `trigger` (string): Trigger type: daily, custom_schedule, or manual
|
|
280
285
|
* `trigger_file` (string): Some MFT services request an empty file (known as a trigger file) to signal the sync is complete and they can begin further processing. If trigger_file is set, a zero-byte file will be sent at the end of the sync.
|
|
286
|
+
* `always_write_trigger_file` (boolean): If true, the trigger file will be sent at the end of a successful sync even when no files were transferred.
|
|
281
287
|
|
|
282
288
|
|
|
283
289
|
---
|
|
@@ -350,7 +356,8 @@ sync.update(
|
|
|
350
356
|
src_remote_server_id: 1,
|
|
351
357
|
sync_interval_minutes: 1,
|
|
352
358
|
trigger: "example",
|
|
353
|
-
trigger_file: "example"
|
|
359
|
+
trigger_file: "example",
|
|
360
|
+
always_write_trigger_file: true
|
|
354
361
|
)
|
|
355
362
|
```
|
|
356
363
|
|
|
@@ -377,6 +384,7 @@ sync.update(
|
|
|
377
384
|
* `sync_interval_minutes` (int64): Frequency in minutes between syncs. If set, this value must be greater than or equal to the `remote_sync_interval` value for the site's plan. If left blank, the plan's `remote_sync_interval` will be used. This setting is only used if `trigger` is empty.
|
|
378
385
|
* `trigger` (string): Trigger type: daily, custom_schedule, or manual
|
|
379
386
|
* `trigger_file` (string): Some MFT services request an empty file (known as a trigger file) to signal the sync is complete and they can begin further processing. If trigger_file is set, a zero-byte file will be sent at the end of the sync.
|
|
387
|
+
* `always_write_trigger_file` (boolean): If true, the trigger file will be sent at the end of a successful sync even when no files were transferred.
|
|
380
388
|
|
|
381
389
|
|
|
382
390
|
---
|
|
@@ -171,6 +171,15 @@ module Files
|
|
|
171
171
|
@attributes[:trigger_file] = value
|
|
172
172
|
end
|
|
173
173
|
|
|
174
|
+
# boolean - If true, the trigger file will be sent at the end of a successful sync even when no files were transferred.
|
|
175
|
+
def always_write_trigger_file
|
|
176
|
+
@attributes[:always_write_trigger_file]
|
|
177
|
+
end
|
|
178
|
+
|
|
179
|
+
def always_write_trigger_file=(value)
|
|
180
|
+
@attributes[:always_write_trigger_file] = value
|
|
181
|
+
end
|
|
182
|
+
|
|
174
183
|
# array(string) - Array of glob patterns to include
|
|
175
184
|
def include_patterns
|
|
176
185
|
@attributes[:include_patterns]
|
|
@@ -314,6 +323,7 @@ module Files
|
|
|
314
323
|
# sync_interval_minutes - int64 - Frequency in minutes between syncs. If set, this value must be greater than or equal to the `remote_sync_interval` value for the site's plan. If left blank, the plan's `remote_sync_interval` will be used. This setting is only used if `trigger` is empty.
|
|
315
324
|
# trigger - string - Trigger type: daily, custom_schedule, or manual
|
|
316
325
|
# trigger_file - string - Some MFT services request an empty file (known as a trigger file) to signal the sync is complete and they can begin further processing. If trigger_file is set, a zero-byte file will be sent at the end of the sync.
|
|
326
|
+
# always_write_trigger_file - boolean - If true, the trigger file will be sent at the end of a successful sync even when no files were transferred.
|
|
317
327
|
def update(params = {})
|
|
318
328
|
params ||= {}
|
|
319
329
|
params[:id] = @attributes[:id]
|
|
@@ -424,6 +434,7 @@ module Files
|
|
|
424
434
|
# sync_interval_minutes - int64 - Frequency in minutes between syncs. If set, this value must be greater than or equal to the `remote_sync_interval` value for the site's plan. If left blank, the plan's `remote_sync_interval` will be used. This setting is only used if `trigger` is empty.
|
|
425
435
|
# trigger - string - Trigger type: daily, custom_schedule, or manual
|
|
426
436
|
# trigger_file - string - Some MFT services request an empty file (known as a trigger file) to signal the sync is complete and they can begin further processing. If trigger_file is set, a zero-byte file will be sent at the end of the sync.
|
|
437
|
+
# always_write_trigger_file - boolean - If true, the trigger file will be sent at the end of a successful sync even when no files were transferred.
|
|
427
438
|
# workspace_id - int64 - Workspace ID this sync belongs to
|
|
428
439
|
def self.create(params = {}, options = {})
|
|
429
440
|
raise InvalidParameterError.new("Bad parameter: description must be an String") if params[:description] and !params[:description].is_a?(String)
|
|
@@ -492,6 +503,7 @@ module Files
|
|
|
492
503
|
# sync_interval_minutes - int64 - Frequency in minutes between syncs. If set, this value must be greater than or equal to the `remote_sync_interval` value for the site's plan. If left blank, the plan's `remote_sync_interval` will be used. This setting is only used if `trigger` is empty.
|
|
493
504
|
# trigger - string - Trigger type: daily, custom_schedule, or manual
|
|
494
505
|
# trigger_file - string - Some MFT services request an empty file (known as a trigger file) to signal the sync is complete and they can begin further processing. If trigger_file is set, a zero-byte file will be sent at the end of the sync.
|
|
506
|
+
# always_write_trigger_file - boolean - If true, the trigger file will be sent at the end of a successful sync even when no files were transferred.
|
|
495
507
|
def self.update(id, params = {}, options = {})
|
|
496
508
|
params ||= {}
|
|
497
509
|
params[:id] = id
|
data/lib/files.com/version.rb
CHANGED