smplkit 1.0.25 → 1.0.26

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c5467982be79b924356216ec4b8a4158589ac70802cefbee82c819f5d390281d
-  data.tar.gz: 93f707d0f9951956db82350eb298d4a14f42ccb2effca770da64f9084e6908d4
+  metadata.gz: 7bdf868508ed91a94310a12e8341733ae453385e42104713e694c60641538bc1
+  data.tar.gz: 003c013da94f5776a03d32458704700bbca466b3b00c6b67b93971bba5e2f746
 SHA512:
-  metadata.gz: 50b0fd8883a16c7b2aff012f26c956a6b5c2f1e3501cb08a02b5641fa360eb1ca60cca85acb0290a141f416497be3a0f0c3a62ced5c6593a357667a149911dec
-  data.tar.gz: 36731f5638835a9939bd712574377f4f6ad7279883ad535f430c986173322c1d30044f95f2b47225c67b85c8eb2d5212ca9e736c4d6f5989b05b8c7260c43d68
+  metadata.gz: a7aec9a8462b8c935bee1467149de3789d168f92fab61862b41ba36e4bded04b32f487110bc509033b77a39b01254c35cd5ed4d903d694d6b62d026d8975f4a9
+  data.tar.gz: 1a4cb3c19a8e58e51a0347d059825b0ff1fe9f9f90350f140cf7a68c2714107d4bcfdc2870b44ee2afd754c993e90454e41101fa046e277b30476952469479e9

data/lib/smplkit/_generated/audit/lib/smplkit_audit_client/api/forwarders_api.rb

@@ -217,7 +217,7 @@ module SmplkitGeneratedClient::Audit
     end
 
     # Get Forwarder
-    # Retrieve a single forwarder by id.  Returns 404 if no forwarder with that id exists in the caller's account, including if the forwarder is soft-deleted. Header values in the response are always redacted regardless of caller permission.
+    # Retrieve a single forwarder by id.  Returns 404 if no forwarder with that id exists in the caller's account, including if the forwarder is soft-deleted. Header values in the response are returned in plaintext so callers can perform a GET-modify-PUT round-trip without re-entering secrets (ADR-014). The persisted ``forwarder_delivery.request`` log column is what keeps redaction; that read path is unaffected by this route.
     # @param forwarder_id [String] 
     # @param [Hash] opts the optional parameters
     # @return [ForwarderResponse]
@@ -227,7 +227,7 @@ module SmplkitGeneratedClient::Audit
     end
 
     # Get Forwarder
-    # Retrieve a single forwarder by id.  Returns 404 if no forwarder with that id exists in the caller's account, including if the forwarder is soft-deleted. Header values in the response are always redacted regardless of caller permission.
+    # Retrieve a single forwarder by id.  Returns 404 if no forwarder with that id exists in the caller's account, including if the forwarder is soft-deleted. Header values in the response are returned in plaintext so callers can perform a GET-modify-PUT round-trip without re-entering secrets (ADR-014). The persisted ``forwarder_delivery.request`` log column is what keeps redaction; that read path is unaffected by this route.
     # @param forwarder_id [String] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(ForwarderResponse, Integer, Hash)>] ForwarderResponse data, response status code and response headers
@@ -564,7 +564,7 @@ module SmplkitGeneratedClient::Audit
     end
 
     # Update Forwarder
-    # Full-replace update. PUT semantics — every field is overwritten.  The header values must be re-supplied; the GET path redacts them, but a PUT body that contains ``\"<redacted>\"`` would persist that literal. Customers must round-trip the actual secret back. This is the standard get-mutate-put pattern (see CLAUDE.md \"Updating Resources via the API\"); the SDK helpers track the un-redacted secret client-side so customers don't usually need to re-enter it.
+    # Full-replace update. PUT semantics — every field is overwritten.  The GET path returns plaintext header values, so the standard get-mutate-put round-trip (ADR-014) preserves secrets without any extra work from the caller: GET, change one field, PUT the result.
     # @param forwarder_id [String] 
     # @param forwarder_response [ForwarderResponse] 
     # @param [Hash] opts the optional parameters
@@ -575,7 +575,7 @@ module SmplkitGeneratedClient::Audit
     end
 
     # Update Forwarder
-    # Full-replace update. PUT semantics — every field is overwritten.  The header values must be re-supplied; the GET path redacts them, but a PUT body that contains &#x60;&#x60;\&quot;&lt;redacted&gt;\&quot;&#x60;&#x60; would persist that literal. Customers must round-trip the actual secret back. This is the standard get-mutate-put pattern (see CLAUDE.md \&quot;Updating Resources via the API\&quot;); the SDK helpers track the un-redacted secret client-side so customers don&#39;t usually need to re-enter it.
+    # Full-replace update. PUT semantics — every field is overwritten.  The GET path returns plaintext header values, so the standard get-mutate-put round-trip (ADR-014) preserves secrets without any extra work from the caller: GET, change one field, PUT the result.
     # @param forwarder_id [String] 
     # @param forwarder_response [ForwarderResponse] 
     # @param [Hash] opts the optional parameters

data/lib/smplkit/_generated/audit/spec/api/forwarders_api_spec.rb

@@ -70,7 +70,7 @@ describe 'ForwardersApi' do
 
   # unit tests for get_forwarder
   # Get Forwarder
-  # Retrieve a single forwarder by id.  Returns 404 if no forwarder with that id exists in the caller's account, including if the forwarder is soft-deleted. Header values in the response are always redacted regardless of caller permission.
+  # Retrieve a single forwarder by id.  Returns 404 if no forwarder with that id exists in the caller's account, including if the forwarder is soft-deleted. Header values in the response are returned in plaintext so callers can perform a GET-modify-PUT round-trip without re-entering secrets (ADR-014). The persisted ``forwarder_delivery.request`` log column is what keeps redaction; that read path is unaffected by this route.
   # @param forwarder_id 
   # @param [Hash] opts the optional parameters
   # @return [ForwarderResponse]
@@ -138,7 +138,7 @@ describe 'ForwardersApi' do
 
   # unit tests for update_forwarder
   # Update Forwarder
-  # Full-replace update. PUT semantics — every field is overwritten.  The header values must be re-supplied; the GET path redacts them, but a PUT body that contains ``\"<redacted>\"`` would persist that literal. Customers must round-trip the actual secret back. This is the standard get-mutate-put pattern (see CLAUDE.md \"Updating Resources via the API\"); the SDK helpers track the un-redacted secret client-side so customers don't usually need to re-enter it.
+  # Full-replace update. PUT semantics — every field is overwritten.  The GET path returns plaintext header values, so the standard get-mutate-put round-trip (ADR-014) preserves secrets without any extra work from the caller: GET, change one field, PUT the result.
   # @param forwarder_id 
   # @param forwarder_response 
   # @param [Hash] opts the optional parameters

metadata

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