smplkit 3.0.86 → 3.0.87

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0ba144ab26f22b115d992b7fa76c62c008959d36428630502aba1fe7b3105a09
-  data.tar.gz: 060a8c1159094f6f06548fab3a5131a73059dfd01f5e36969a1c9a9ec9024295
+  metadata.gz: c2fdb5a80c9783bf884e828769eb3474b2006337a2850d31f3e7db99ffd42d14
+  data.tar.gz: 4d8d2f80f0f7b77744c34c09fe0a73215e80ebb7049a630a6d068b0d7c860826
 SHA512:
-  metadata.gz: 7d93149c62b6f42b374a9981cd626de920ddb40cd66f4bb1895cd76a38d5b4ce7b5e89714297a85d0b02c1b5279402dacd9b2e436ce85b44e2a940027f45efab
-  data.tar.gz: 4925d4755f91c0e2efaa87ed19e356604d4eef5bd73d2a937a83103e7977c2fd545071ea4c4feb8612fc2e09eaacac3cac1482a2fe4ffaf001fa082768ab38fd
+  metadata.gz: 163879655a41a24c1aaeeb74c36d3ad0f7cbb7ddb9253c1a64e213e596dbd6ae3ecfb6819b3f2f60d648677c1e36a1491ec1c4c4c757722d1ad7e7c08934b58b
+  data.tar.gz: '058b6d8e3509ec5a2cd476c33b61ae16c2f2346bac8b2fdb5a1a64c78a5dac3730c57db03a2063d557e3f65266d4030d7626895a2703310881512dd2ee2cfc96'

data/lib/smplkit/_generated/audit/lib/smplkit_audit_client/models/http_configuration.rb

@@ -14,18 +14,18 @@ require 'date'
 require 'time'
 
 module SmplkitGeneratedClient::Audit
-  # HTTP request configuration used to deliver an event to the destination.  Used when the parent forwarder's ``forwarder_type`` is one of the HTTP-family destinations (``HTTP``, ``DATADOG``, ``SPLUNK_HEC``, ``SUMO_LOGIC``, ``NEW_RELIC``, ``HONEYCOMB``, ``ELASTIC``). When other transports land (``FTP``, ``SQS``, …) their own configuration schemas will join this one as members of a discriminated union under the ``configuration`` field of ``Forwarder``.
+  # HTTP request configuration for delivering a payload to a destination.  The shared base shape for any product that posts to a customer-supplied HTTP destination. Smpl Audit forwarders use it directly; Smpl Jobs extends it (adding ``body`` and ``timeout``). When other transports land (``FTP``, ``SQS``, …) their own configuration schemas will join this one as members of a discriminated union under a ``configuration`` field.
   class HttpConfiguration < ApiModelBase
-    # HTTP method used when delivering an event.
+    # HTTP method used when delivering the request.
     attr_accessor :method
 
     # Destination URL. Must be an absolute `http://` or `https://` URL with a hostname (e.g. `https://siem.example.com/in`).
     attr_accessor :url
 
-    # HTTP headers attached to each delivery request.
+    # HTTP headers attached to each request.
     attr_accessor :headers
 
-    # HTTP response status that indicates a successful delivery. Either a specific status code (e.g. `200`, `204`) or a status class (`1xx`, `2xx`, `3xx`, `4xx`, `5xx`).
+    # HTTP response status that indicates success. Either a specific status code (e.g. `200`, `204`) or a status class (`1xx`, `2xx`, `3xx`, `4xx`, `5xx`).
     attr_accessor :success_status
 
     # Whether to verify the destination server's TLS certificate against trusted certificate authorities. Defaults to `true` and should be left on for any production destination. Set to `false` only for development or short-lived testing against a destination that presents an untrusted certificate (e.g. a Splunk Cloud trial stack on `:8088` serving its default self-signed certificate). When `false`, deliveries proceed without certificate verification — they are vulnerable to man-in-the-middle attacks. For long-lived self-signed setups, pin the issuing CA via `ca_cert` instead of disabling verification entirely.

data/lib/smplkit/_generated/audit/lib/smplkit_audit_client/models/http_header.rb

@@ -14,7 +14,7 @@ require 'date'
 require 'time'
 
 module SmplkitGeneratedClient::Audit
-  # A single HTTP header attached to a forwarder delivery request.  Header values are encrypted at the application layer before persistence regardless of header name; the wire representation here is always plaintext on both the request and the response, so a `GET → mutate → PUT` round-trip preserves header values without requiring the customer to re-enter secrets.
+  # A single HTTP header attached to an outbound request.  Header values are encrypted at the application layer before persistence regardless of header name; the wire representation here is always plaintext on both the request and the response, so a `GET → mutate → PUT` round-trip preserves header values without requiring the customer to re-enter secrets.
   class HttpHeader < ApiModelBase
     # Header name.
     attr_accessor :name

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: smplkit
 version: !ruby/object:Gem::Version
-  version: 3.0.86
+  version: 3.0.87
 platform: ruby
 authors:
 - Smpl Solutions LLC