files.com 1.2.280 → 1.2.282

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.
package/_VERSION CHANGED
@@ -1 +1 @@
1
- 1.2.280
1
+ 1.2.282
@@ -25,7 +25,11 @@
25
25
  "created_at": "2000-01-01T01:00:00Z",
26
26
  "destination": "/to_path",
27
27
  "path": "",
28
- "source": "/from_path"
28
+ "source": "/from_path",
29
+ "bundle_registration_id": 1,
30
+ "bundle_registration_name": "John Doe",
31
+ "bundle_registration_email": "john@example.com",
32
+ "bundle_registration_ip": "127.0.0.1"
29
33
  }
30
34
  ```
31
35
 
@@ -35,6 +39,10 @@
35
39
  * `destination` (string): The destination path for this bundle action, if applicable
36
40
  * `path` (string): Path. This must be slash-delimited, but it must neither start nor end with a slash. Maximum of 5000 characters.
37
41
  * `source` (string): The source path for this bundle action, if applicable
42
+ * `bundle_registration_id` (int64): Identifier of the associated bundle registration
43
+ * `bundle_registration_name` (string): Name of the registrant who performed the action
44
+ * `bundle_registration_email` (string): Email of the registrant
45
+ * `bundle_registration_ip` (string): IP address of the registrant
38
46
 
39
47
  ---
40
48
 
@@ -52,7 +60,7 @@ await BundleAction.list({
52
60
  * `user_id` (int64): User ID. Provide a value of `0` to operate the current session's user.
53
61
  * `cursor` (string): Used for pagination. When a list request has more records available, cursors are provided in the response headers `X-Files-Cursor-Next` and `X-Files-Cursor-Prev`. Send one of those cursor value here to resume an existing list from the next available record. Note: many of our SDKs have iterator methods that will automatically handle cursor-based pagination.
54
62
  * `per_page` (int64): Number of records to show per page. (Max: 10,000, 1,000 or less is recommended).
55
- * `sort_by` (object): If set, sort records by the specified field in either `asc` or `desc` direction. Valid fields are `created_at`.
63
+ * `sort_by` (object): If set, sort records by the specified field in either `asc` or `desc` direction. Valid fields are `created_at` and `bundle_registration_id`.
56
64
  * `filter` (object): If set, return records where the specified field is equal to the supplied value. Valid fields are `created_at`, `bundle_id` or `bundle_registration_id`. Valid field combinations are `[ bundle_id, created_at ]`, `[ bundle_registration_id, created_at ]`, `[ bundle_id, bundle_registration_id ]` or `[ bundle_id, bundle_registration_id, created_at ]`.
57
65
  * `filter_gt` (object): If set, return records where the specified field is greater than the supplied value. Valid fields are `created_at`.
58
66
  * `filter_gteq` (object): If set, return records where the specified field is greater than or equal the supplied value. Valid fields are `created_at`.
@@ -453,7 +453,7 @@
453
453
  * `ssl_required` (boolean): Is SSL required? Disabling this is insecure.
454
454
  * `subdomain` (string): Site subdomain
455
455
  * `switch_to_plan_date` (date-time): If switching plans, when does the new plan take effect?
456
- * `tls_disabled` (boolean): DO NOT ENABLE. This setting allows TLSv1.0 and TLSv1.1 to be used on your site. We intend to remove this capability entirely in early 2024. If set, the `sftp_insecure_ciphers` flag will be automatically set to true.
456
+ * `tls_disabled` (boolean): This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP. See our documentation for more information. Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
457
457
  * `trial_days_left` (int64): Number of days left in trial
458
458
  * `trial_until` (date-time): When does this Site trial expire?
459
459
  * `use_dedicated_ips_for_smtp` (boolean): If using custom SMTP, should we use dedicated IPs to deliver emails?
@@ -703,7 +703,7 @@ await Site.update({
703
703
  * `migrate_remote_server_sync_to_sync` (boolean): If true, we will migrate all remote server syncs to the new Sync model.
704
704
  * `session_expiry` (double): Session expiry in hours
705
705
  * `ssl_required` (boolean): Is SSL required? Disabling this is insecure.
706
- * `tls_disabled` (boolean): DO NOT ENABLE. This setting allows TLSv1.0 and TLSv1.1 to be used on your site. We intend to remove this capability entirely in early 2024. If set, the `sftp_insecure_ciphers` flag will be automatically set to true.
706
+ * `tls_disabled` (boolean): This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP. See our documentation for more information. Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
707
707
  * `sftp_insecure_ciphers` (boolean): If true, we will allow weak and known insecure ciphers to be used for SFTP connections. Enabling this setting severely weakens the security of your site and it is not recommend, except as a last resort for compatibility.
708
708
  * `sftp_insecure_diffie_hellman` (boolean): If true, we will allow weak Diffie Hellman parameters to be used within ciphers for SFTP that are otherwise on our secure list. This has the effect of making the cipher weaker than our normal threshold for security, but is required to support certain legacy or broken SSH and MFT clients. Enabling this weakens security, but not nearly as much as enabling the full `sftp_insecure_ciphers` option.
709
709
  * `disable_files_certificate_generation` (boolean): If set, Files.com will not set the CAA records required to generate future SSL certificates for this domain.
package/lib/Files.js CHANGED
@@ -12,7 +12,7 @@ var apiKey;
12
12
  var baseUrl = 'https://app.files.com';
13
13
  var sessionId = null;
14
14
  var language = null;
15
- var version = '1.2.280';
15
+ var version = '1.2.282';
16
16
  var userAgent = "Files.com JavaScript SDK v".concat(version);
17
17
  var logLevel = _Logger.LogLevel.INFO;
18
18
  var debugRequest = false;
@@ -56,6 +56,22 @@ var BundleAction = /*#__PURE__*/(0, _createClass2.default)(function BundleAction
56
56
  (0, _defineProperty2.default)(this, "getSource", function () {
57
57
  return _this.attributes.source;
58
58
  });
59
+ // int64 # Identifier of the associated bundle registration
60
+ (0, _defineProperty2.default)(this, "getBundleRegistrationId", function () {
61
+ return _this.attributes.bundle_registration_id;
62
+ });
63
+ // string # Name of the registrant who performed the action
64
+ (0, _defineProperty2.default)(this, "getBundleRegistrationName", function () {
65
+ return _this.attributes.bundle_registration_name;
66
+ });
67
+ // string # Email of the registrant
68
+ (0, _defineProperty2.default)(this, "getBundleRegistrationEmail", function () {
69
+ return _this.attributes.bundle_registration_email;
70
+ });
71
+ // string # IP address of the registrant
72
+ (0, _defineProperty2.default)(this, "getBundleRegistrationIp", function () {
73
+ return _this.attributes.bundle_registration_ip;
74
+ });
59
75
  Object.entries(attributes).forEach(function (_ref) {
60
76
  var _ref2 = (0, _slicedToArray2.default)(_ref, 2),
61
77
  key = _ref2[0],
@@ -74,7 +90,7 @@ _BundleAction = BundleAction;
74
90
  // user_id - int64 - User ID. Provide a value of `0` to operate the current session's user.
75
91
  // cursor - string - Used for pagination. When a list request has more records available, cursors are provided in the response headers `X-Files-Cursor-Next` and `X-Files-Cursor-Prev`. Send one of those cursor value here to resume an existing list from the next available record. Note: many of our SDKs have iterator methods that will automatically handle cursor-based pagination.
76
92
  // per_page - int64 - Number of records to show per page. (Max: 10,000, 1,000 or less is recommended).
77
- // sort_by - object - If set, sort records by the specified field in either `asc` or `desc` direction. Valid fields are `created_at`.
93
+ // sort_by - object - If set, sort records by the specified field in either `asc` or `desc` direction. Valid fields are `created_at` and `bundle_registration_id`.
78
94
  // filter - object - If set, return records where the specified field is equal to the supplied value. Valid fields are `created_at`, `bundle_id` or `bundle_registration_id`. Valid field combinations are `[ bundle_id, created_at ]`, `[ bundle_registration_id, created_at ]`, `[ bundle_id, bundle_registration_id ]` or `[ bundle_id, bundle_registration_id, created_at ]`.
79
95
  // filter_gt - object - If set, return records where the specified field is greater than the supplied value. Valid fields are `created_at`.
80
96
  // filter_gteq - object - If set, return records where the specified field is greater than or equal the supplied value. Valid fields are `created_at`.
@@ -628,7 +628,7 @@ var Site = /*#__PURE__*/(0, _createClass2.default)(function Site() {
628
628
  (0, _defineProperty2.default)(this, "getSwitchToPlanDate", function () {
629
629
  return _this.attributes.switch_to_plan_date;
630
630
  });
631
- // boolean # DO NOT ENABLE. This setting allows TLSv1.0 and TLSv1.1 to be used on your site. We intend to remove this capability entirely in early 2024. If set, the `sftp_insecure_ciphers` flag will be automatically set to true.
631
+ // boolean # This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP. See our documentation for more information. Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
632
632
  (0, _defineProperty2.default)(this, "getTlsDisabled", function () {
633
633
  return _this.attributes.tls_disabled;
634
634
  });
@@ -812,7 +812,7 @@ _Site = Site;
812
812
  // migrate_remote_server_sync_to_sync - boolean - If true, we will migrate all remote server syncs to the new Sync model.
813
813
  // session_expiry - double - Session expiry in hours
814
814
  // ssl_required - boolean - Is SSL required? Disabling this is insecure.
815
- // tls_disabled - boolean - DO NOT ENABLE. This setting allows TLSv1.0 and TLSv1.1 to be used on your site. We intend to remove this capability entirely in early 2024. If set, the `sftp_insecure_ciphers` flag will be automatically set to true.
815
+ // tls_disabled - boolean - This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP. See our documentation for more information. Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
816
816
  // sftp_insecure_ciphers - boolean - If true, we will allow weak and known insecure ciphers to be used for SFTP connections. Enabling this setting severely weakens the security of your site and it is not recommend, except as a last resort for compatibility.
817
817
  // sftp_insecure_diffie_hellman - boolean - If true, we will allow weak Diffie Hellman parameters to be used within ciphers for SFTP that are otherwise on our secure list. This has the effect of making the cipher weaker than our normal threshold for security, but is required to support certain legacy or broken SSH and MFT clients. Enabling this weakens security, but not nearly as much as enabling the full `sftp_insecure_ciphers` option.
818
818
  // disable_files_certificate_generation - boolean - If set, Files.com will not set the CAA records required to generate future SSL certificates for this domain.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "files.com",
3
- "version": "1.2.280",
3
+ "version": "1.2.282",
4
4
  "description": "Files.com SDK for JavaScript",
5
5
  "keywords": [
6
6
  "files.com",
package/src/Files.js CHANGED
@@ -6,7 +6,7 @@ let apiKey
6
6
  let baseUrl = 'https://app.files.com'
7
7
  let sessionId = null
8
8
  let language = null
9
- const version = '1.2.280'
9
+ const version = '1.2.282'
10
10
  let userAgent = `Files.com JavaScript SDK v${version}`
11
11
 
12
12
  let logLevel = LogLevel.INFO
@@ -46,11 +46,23 @@ class BundleAction {
46
46
  // string # The source path for this bundle action, if applicable
47
47
  getSource = () => this.attributes.source
48
48
 
49
+ // int64 # Identifier of the associated bundle registration
50
+ getBundleRegistrationId = () => this.attributes.bundle_registration_id
51
+
52
+ // string # Name of the registrant who performed the action
53
+ getBundleRegistrationName = () => this.attributes.bundle_registration_name
54
+
55
+ // string # Email of the registrant
56
+ getBundleRegistrationEmail = () => this.attributes.bundle_registration_email
57
+
58
+ // string # IP address of the registrant
59
+ getBundleRegistrationIp = () => this.attributes.bundle_registration_ip
60
+
49
61
  // Parameters:
50
62
  // user_id - int64 - User ID. Provide a value of `0` to operate the current session's user.
51
63
  // cursor - string - Used for pagination. When a list request has more records available, cursors are provided in the response headers `X-Files-Cursor-Next` and `X-Files-Cursor-Prev`. Send one of those cursor value here to resume an existing list from the next available record. Note: many of our SDKs have iterator methods that will automatically handle cursor-based pagination.
52
64
  // per_page - int64 - Number of records to show per page. (Max: 10,000, 1,000 or less is recommended).
53
- // sort_by - object - If set, sort records by the specified field in either `asc` or `desc` direction. Valid fields are `created_at`.
65
+ // sort_by - object - If set, sort records by the specified field in either `asc` or `desc` direction. Valid fields are `created_at` and `bundle_registration_id`.
54
66
  // filter - object - If set, return records where the specified field is equal to the supplied value. Valid fields are `created_at`, `bundle_id` or `bundle_registration_id`. Valid field combinations are `[ bundle_id, created_at ]`, `[ bundle_registration_id, created_at ]`, `[ bundle_id, bundle_registration_id ]` or `[ bundle_id, bundle_registration_id, created_at ]`.
55
67
  // filter_gt - object - If set, return records where the specified field is greater than the supplied value. Valid fields are `created_at`.
56
68
  // filter_gteq - object - If set, return records where the specified field is greater than or equal the supplied value. Valid fields are `created_at`.
@@ -475,7 +475,7 @@ class Site {
475
475
  // date-time # If switching plans, when does the new plan take effect?
476
476
  getSwitchToPlanDate = () => this.attributes.switch_to_plan_date
477
477
 
478
- // boolean # DO NOT ENABLE. This setting allows TLSv1.0 and TLSv1.1 to be used on your site. We intend to remove this capability entirely in early 2024. If set, the `sftp_insecure_ciphers` flag will be automatically set to true.
478
+ // boolean # This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP. See our documentation for more information. Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
479
479
  getTlsDisabled = () => this.attributes.tls_disabled
480
480
 
481
481
  // int64 # Number of days left in trial
@@ -597,7 +597,7 @@ class Site {
597
597
  // migrate_remote_server_sync_to_sync - boolean - If true, we will migrate all remote server syncs to the new Sync model.
598
598
  // session_expiry - double - Session expiry in hours
599
599
  // ssl_required - boolean - Is SSL required? Disabling this is insecure.
600
- // tls_disabled - boolean - DO NOT ENABLE. This setting allows TLSv1.0 and TLSv1.1 to be used on your site. We intend to remove this capability entirely in early 2024. If set, the `sftp_insecure_ciphers` flag will be automatically set to true.
600
+ // tls_disabled - boolean - This setting enables Legacy Support for Insecure Ciphers across SFTP and FTP. See our documentation for more information. Contrary to its name, this setting does not disable TLS (it used to do that a long time ago), but rather enables certain ciphers which are known to be insecure but required for broad MFT compatibility.
601
601
  // sftp_insecure_ciphers - boolean - If true, we will allow weak and known insecure ciphers to be used for SFTP connections. Enabling this setting severely weakens the security of your site and it is not recommend, except as a last resort for compatibility.
602
602
  // sftp_insecure_diffie_hellman - boolean - If true, we will allow weak Diffie Hellman parameters to be used within ciphers for SFTP that are otherwise on our secure list. This has the effect of making the cipher weaker than our normal threshold for security, but is required to support certain legacy or broken SSH and MFT clients. Enabling this weakens security, but not nearly as much as enabling the full `sftp_insecure_ciphers` option.
603
603
  // disable_files_certificate_generation - boolean - If set, Files.com will not set the CAA records required to generate future SSL certificates for this domain.