files.com 1.1.773 → 1.1.775

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 07f3cc24cf0891a91c9feaf9fdeeae39301d8b23a32207616eba7db5cc070ace
-  data.tar.gz: b1619f673e77c0a9423c8083ec425a6ea26f61cd9a1d6aa9629be3d6e0f70cf6
+  metadata.gz: d4c219d136b284a59d807f0457203b8c9cea7dfc0a2e816df7be244d5a063546
+  data.tar.gz: 92418b15c3786ca448d176d68a3e1d2a9a16e1a9c69a0c8713642e37c87b7f74
 SHA512:
-  metadata.gz: 85ca525bf43d05c3cf61e12aaea2fc9c22a97f8b2c31a8e136e6840d7578e8e88bb703d49c850068286195f89bf5c943371dead5f15ab813cae0a700f661e1f5
-  data.tar.gz: 4fad3a9f835494fc420493feac4aed82c9ad1d4a23a14674fffdcaece12c3d5ba5480b53a60a337851d5a1bfcc840cae3b4988eabe7c58c8123f131091bcf9fc
+  metadata.gz: aa90b8947359abecb1f93143a999a5816d291bba7d3087966baaaa695acc90f02a4c0d5b73ebbd7a34c93f831d815809995b6f977159ffeb74573169236adeb2
+  data.tar.gz: c160181dd3b0241c69b86a86d11afb2f2a73a83f3c17c8ac913aabea1d9c5307981c267f7f8dd01839924591cdeefde9f522127938d71df3217ba0b6df26c7b2

data/README.md

@@ -67,7 +67,7 @@ the method used in the examples on this site.
 
 To use an API Key, first generate an API key from the [web
 interface](https://www.files.com/docs/sdk-and-apis/api-keys) or [via the API or an
-SDK](/ruby/resources/developers/api-keys).
+SDK](https://developers.files.com/ruby/resources/developers/api-keys).
 
 Note that when using a user-specific API key, if the user is an administrator, you will have full
 access to the entire API. If the user is not an administrator, you will only be able to access files

data/_VERSION

@@ -1 +1 @@
-1.1.773
+1.1.775

data/docs/as2_partner.md

@@ -39,7 +39,7 @@
 * `additional_http_headers` (object): Additional HTTP Headers for outgoing message sent to this partner.
 * `default_mime_type` (string): Default mime type of the file attached to the encrypted message
 * `mdn_validation_level` (string): How should Files.com evaluate message transfer success based on a partner's MDN response?  This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates. `auto`: Automatically set the correct value for this setting based on next mdn received.
-* `signature_validation_level` (string): Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: Automatically set the correct value for this setting based on next message received.
+* `signature_validation_level` (string): Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: A one-time starting state. The next message received is always accepted and switches this to `normal` if it carries a valid signature, or `none` if it does not.
 * `enable_dedicated_ips` (boolean): If `true`, we will use your site's dedicated IPs for all outbound connections to this AS2 Partner.
 * `hex_public_certificate_serial` (string): Serial of public certificate used for message security in hex format.
 * `public_certificate` (string): Public certificate used for message security.
@@ -109,7 +109,7 @@ Files::As2Partner.create(
 * `http_auth_username` (string): Username to send to server for HTTP Authentication.
 * `http_auth_password` (string): Password to send to server for HTTP Authentication.
 * `mdn_validation_level` (string): How should Files.com evaluate message transfer success based on a partner's MDN response?  This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates. `auto`: Automatically set the correct value for this setting based on next mdn received.
-* `signature_validation_level` (string): Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: Automatically set the correct value for this setting based on next message received.
+* `signature_validation_level` (string): Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: A one-time starting state. The next message received is always accepted and switches this to `normal` if it carries a valid signature, or `none` if it does not.
 * `server_certificate` (string): Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
 * `default_mime_type` (string): Default mime type of the file attached to the encrypted message
 * `additional_http_headers` (object): Additional HTTP Headers for outgoing message sent to this partner.
@@ -147,7 +147,7 @@ Files::As2Partner.update(id,
 * `http_auth_username` (string): Username to send to server for HTTP Authentication.
 * `http_auth_password` (string): Password to send to server for HTTP Authentication.
 * `mdn_validation_level` (string): How should Files.com evaluate message transfer success based on a partner's MDN response?  This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates. `auto`: Automatically set the correct value for this setting based on next mdn received.
-* `signature_validation_level` (string): Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: Automatically set the correct value for this setting based on next message received.
+* `signature_validation_level` (string): Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: A one-time starting state. The next message received is always accepted and switches this to `normal` if it carries a valid signature, or `none` if it does not.
 * `server_certificate` (string): Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
 * `default_mime_type` (string): Default mime type of the file attached to the encrypted message
 * `additional_http_headers` (object): Additional HTTP Headers for outgoing message sent to this partner.
@@ -199,7 +199,7 @@ as2_partner.update(
 * `http_auth_username` (string): Username to send to server for HTTP Authentication.
 * `http_auth_password` (string): Password to send to server for HTTP Authentication.
 * `mdn_validation_level` (string): How should Files.com evaluate message transfer success based on a partner's MDN response?  This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates. `auto`: Automatically set the correct value for this setting based on next mdn received.
-* `signature_validation_level` (string): Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: Automatically set the correct value for this setting based on next message received.
+* `signature_validation_level` (string): Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: A one-time starting state. The next message received is always accepted and switches this to `normal` if it carries a valid signature, or `none` if it does not.
 * `server_certificate` (string): Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
 * `default_mime_type` (string): Default mime type of the file attached to the encrypted message
 * `additional_http_headers` (object): Additional HTTP Headers for outgoing message sent to this partner.

data/docs/file.md

@@ -282,6 +282,22 @@ Files::File.zip_list_contents(path)
 * `path` (string): Required - Path to operate on.
 
 
+---
+
+## Delete File/Folder and return its File Action.  A pending or processing deletion continues in the background after this returns; check its File Migration for completion.  Waiting for the File Migration does not cancel the deletion
+
+```
+Files::File.begin_delete(path, 
+  recursive: false
+)
+```
+
+### Parameters
+
+* `path` (string): Required - Path to operate on.
+* `recursive` (boolean): If true, will recursively delete folders.  Otherwise, will error on non-empty folders.
+
+
 ---
 
 ## Copy File/Folder
@@ -548,6 +564,24 @@ file.zip_list_contents
 * `path` (string): Required - Path to operate on.
 
 
+---
+
+## Delete File/Folder and return its File Action.  A pending or processing deletion continues in the background after this returns; check its File Migration for completion.  Waiting for the File Migration does not cancel the deletion
+
+```
+file = Files::File.find(path)
+
+file.begin_delete(
+  recursive: false
+)
+```
+
+### Parameters
+
+* `path` (string): Required - Path to operate on.
+* `recursive` (boolean): If true, will recursively delete folders.  Otherwise, will error on non-empty folders.
+
+
 ---
 
 ## Copy File/Folder

data/docs/file_action.md

@@ -10,4 +10,4 @@
 ```
 
 * `status` (string): Status of file operation.
-* `file_migration_id` (int64): If status is pending, this is the id of the File Migration to check for status updates.
+* `file_migration_id` (int64): If status is pending, this is the id of the File Migration to check for status updates.  Delete actions include it whenever the deletion runs as a File Migration, including while it is processing.

data/lib/files.com/models/as2_partner.rb

@@ -99,7 +99,7 @@ module Files
       @attributes[:mdn_validation_level] = value
     end
 
-    # string - Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: Automatically set the correct value for this setting based on next message received.
+    # string - Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: A one-time starting state. The next message received is always accepted and switches this to `normal` if it carries a valid signature, or `none` if it does not.
     def signature_validation_level
       @attributes[:signature_validation_level]
     end
@@ -221,7 +221,7 @@ module Files
     #   http_auth_username - string - Username to send to server for HTTP Authentication.
     #   http_auth_password - string - Password to send to server for HTTP Authentication.
     #   mdn_validation_level - string - How should Files.com evaluate message transfer success based on a partner's MDN response?  This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates. `auto`: Automatically set the correct value for this setting based on next mdn received.
-    #   signature_validation_level - string - Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: Automatically set the correct value for this setting based on next message received.
+    #   signature_validation_level - string - Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: A one-time starting state. The next message received is always accepted and switches this to `normal` if it carries a valid signature, or `none` if it does not.
     #   server_certificate - string - Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
     #   default_mime_type - string - Default mime type of the file attached to the encrypted message
     #   additional_http_headers - object - Additional HTTP Headers for outgoing message sent to this partner.
@@ -332,7 +332,7 @@ module Files
     #   http_auth_username - string - Username to send to server for HTTP Authentication.
     #   http_auth_password - string - Password to send to server for HTTP Authentication.
     #   mdn_validation_level - string - How should Files.com evaluate message transfer success based on a partner's MDN response?  This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates. `auto`: Automatically set the correct value for this setting based on next mdn received.
-    #   signature_validation_level - string - Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: Automatically set the correct value for this setting based on next message received.
+    #   signature_validation_level - string - Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: A one-time starting state. The next message received is always accepted and switches this to `normal` if it carries a valid signature, or `none` if it does not.
     #   server_certificate - string - Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
     #   default_mime_type - string - Default mime type of the file attached to the encrypted message
     #   additional_http_headers - object - Additional HTTP Headers for outgoing message sent to this partner.
@@ -374,7 +374,7 @@ module Files
     #   http_auth_username - string - Username to send to server for HTTP Authentication.
     #   http_auth_password - string - Password to send to server for HTTP Authentication.
     #   mdn_validation_level - string - How should Files.com evaluate message transfer success based on a partner's MDN response?  This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates. `auto`: Automatically set the correct value for this setting based on next mdn received.
-    #   signature_validation_level - string - Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: Automatically set the correct value for this setting based on next message received.
+    #   signature_validation_level - string - Should Files.com require signatures on incoming AS2 messages?  `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: A one-time starting state. The next message received is always accepted and switches this to `normal` if it carries a valid signature, or `none` if it does not.
     #   server_certificate - string - Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
     #   default_mime_type - string - Default mime type of the file attached to the encrypted message
     #   additional_http_headers - object - Additional HTTP Headers for outgoing message sent to this partner.

data/lib/files.com/models/file.rb

@@ -1145,6 +1145,20 @@ module Files
       Api.send_request("/file_actions/zip_list/#{@attributes[:path]}", :get, params, @options)
     end
 
+    # Delete File/Folder and return its File Action.  A pending or processing deletion continues in the background after this returns; check its File Migration for completion.  Waiting for the File Migration does not cancel the deletion
+    #
+    # Parameters:
+    #   recursive - boolean - If true, will recursively delete folders.  Otherwise, will error on non-empty folders.
+    def begin_delete(params = {})
+      params ||= {}
+      params[:path] = @attributes[:path]
+      raise MissingParameterError.new("Current object doesn't have a path") unless @attributes[:path]
+      raise InvalidParameterError.new("Bad parameter: path must be an String") if params[:path] and !params[:path].is_a?(String)
+      raise MissingParameterError.new("Parameter missing: path") unless params[:path]
+
+      Api.send_request("/file_actions/delete/#{@attributes[:path]}", :post, params, @options)
+    end
+
     # Copy File/Folder
     #
     # Parameters:
@@ -1466,6 +1480,25 @@ module Files
       end
     end
 
+    # Delete File/Folder and return its File Action.  A pending or processing deletion continues in the background after this returns; check its File Migration for completion.  Waiting for the File Migration does not cancel the deletion
+    #
+    # Parameters:
+    #   recursive - boolean - If true, will recursively delete folders.  Otherwise, will error on non-empty folders.
+    #
+    # params:: Hash of API operation parameter values.
+    # options:: Hash of optional request configuration passed to Files::Api.send_request.
+    #
+    # Returns a Files::FileAction.
+    def self.begin_delete(path, params = {}, options = {})
+      params ||= {}
+      params[:path] = path
+      raise InvalidParameterError.new("Bad parameter: path must be an String") if params[:path] and !params[:path].is_a?(String)
+      raise MissingParameterError.new("Parameter missing: path") unless params[:path]
+
+      response, options = Api.send_request("/file_actions/delete/#{params[:path]}", :post, params, options) { |reply| reply.require_object("FileAction") }
+      FileAction.new(response.data, options)
+    end
+
     # Copy File/Folder
     #
     # Parameters:

data/lib/files.com/models/file_action.rb

@@ -14,7 +14,7 @@ module Files
       @attributes[:status]
     end
 
-    # int64 - If status is pending, this is the id of the File Migration to check for status updates.
+    # int64 - If status is pending, this is the id of the File Migration to check for status updates.  Delete actions include it whenever the deletion runs as a File Migration, including while it is processing.
     def file_migration_id
       @attributes[:file_migration_id]
     end

data/lib/files.com/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Files
-  VERSION = "1.1.773"
+  VERSION = "1.1.775"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: files.com
 version: !ruby/object:Gem::Version
-  version: 1.1.773
+  version: 1.1.775
 platform: ruby
 authors:
 - files.com
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2026-10-09 00:00:00.000000000 Z
+date: 2026-10-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: addressable