Snap Pack history: API Suite
|
|
|
Updates |
|---|---|---|---|
|
|
|
Enhanced the gRPC Client Snap to support the OAuth2 Account for all the Grant types (Authorization code, Client Credentials, and Password) to enable integration with gRPC services. |
|
|
|
Fixed an issue with the SSL Account , which returned No required TLS certificate was sent when the Trust all certificates checkbox is selected. The keystore provided is now added to the SSLContext. |
|
|
|
|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed a 403 error (request failure issue) in the HTTP Client Snap when proxy is defined and the request host is part of non-proxy hosts. |
|
|
|
Fixed an issue with the HTTP Client Snap where the Snap displayed an error when the query parameters were empty. |
|
|
|
Fixed an issue with the HTTP Client Snap caused by appending a UTF-8 charset to Content-Type for text/html, which conflicted with the endpoint's supported file types (.htm, .html). This is applicable only when you send charset as part of file content. |
|
|
|
Fixed a null pointer exception with the HTTP Client Snap when requests contained no response. |
|
|
|
Fixed the following issues with the
HTTP Client
Snap:
|
|
|
|
Fixed the following issues in the
HTTP Client
Snap:
|
|
|
|
Enhanced the HTTP Client Snap to support uploading of a multipart file from external file systems. Learn more. |
|
|
|
|
|
|
|
|
|
|
|
Fixed an issue with the GraphQL Client Snap that caused Vertx thread leaks and DatagramSocket exhaustion. |
|
|
|
Fixed an issue with the GraphQL Client Snap where the Snap did not route the 400/404/500 errors to the error view. Now, the Snap routes the error data to the error view when these errors occur. |
|
|
|
|
|
|
|
Enhanced the GraphQL Client Snap to support expressions (pipeline and upstream parameters) for the Query, Has additional page path and Next cursor path fields that enable you to dynamically pass values to the Snap. This feature allows you to decrease development and maintenance costs and increase flexibility. This has resulted in specific behavior changes. |
|
|
|
Fixed an issue with the
GraphQL Client
Snap
for InvalidResponseException in case of 401 errors. Now, the Snap
correctly displays errors when a 401 or 403 error occurs. This ensures that the Snap
behaves as expected, even when a GraphQL request returns a 200 response code but
contains unwanted elements in the response.Note:
Behavior change: The GraphQL Client Snap now retires 401 responses by reloading the account between attempts. If the maximum number of attempts is exhausted and the response still contains a 401, the Snap stops the execution instead of writing to the error view because the error is now unrecoverable. Fixed an issue with the HTTP Client Snap that failed when the URI field contained an underscore (_) in the hostname, resulting in an empty hostname. Now the Snap works as expected when the hostname contains underscores. |
|
|
|
|
|
|
|
Added the gRPC Client Snap that enables you to interact with a gRPC (Google Remote Procedure Call) server to invoke its services. Learn more. |
|
|
|
|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed a token refresh issue with the GraphQL Client Snap (configured with the OAuth2 Account ) wherein the access token expired before the periodic platform refresh, and the Snap displayed 401 and 403 errors. Now, the account refreshes the access token and retries query execution, ensuring seamless integration. |
|
|
|
|
|
|
|
Enhanced the HTTP Client Snap with improved handling of redirect URL encoding to minimize runtime errors.By default, the Snap executes the standard redirect behavior. However, if a redirect URL contains unencoded spaces, or special characters, or any other improper format that could potentially cause issues, the Snap encodes the URL before redirecting, ensuring a successful runtime execution. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Updated the API Suite Snaps to process authentication information from incoming documents to support features such as Secrets manager-based credentials. |
|
|
|
Fixed an issue with the
HTTP Client
Snap that
caused NullPointerException when the Retry-After
header contained a decimal value in the 429 (Too Many Requests)
response. |
|
|
|
Fixed an issue with the HTTP Client where redirect URLs containing spaces were not properly encoded, resulting in runtime errors. |
|
|
|
Enhanced the SSL OAuth2 Account Account with the Send Client Data as Basic Auth header checkbox that enables you to send the client information as a header to the OAuth endpoint. |
|
|
|
Enhanced the OAuth2 Account with Snaplex support for executing OAuth2 operations. |
|
|
|
Fixed an issue with the
GraphQL Client
Snap
that displayed an error when passing the Float data type query
variables to the endpoint. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Enhanced the
HTTP Client
Snap to optimize the
memory usage by accumulating the Request History objects only when
you select the Enable debug checkbox. Now, the Snap displays debug
information and lint warnings only (in both Error view and Output view) when you
select the Enable debug checkbox. |
|
|
|
Enhanced the GraphQL Client Snap to include detailed stack trace, error message, and reason within the Snap error view output. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue that caused the HTTP Client Snap to fail when the Basic Authentication Account password contained special characters. |
|
|
|
|
|
|
|
Fixed an issue with the
HTTP Client
Snap that
caused incorrect parsing of the boundary parameter by some REST
endpoints. If you need to specify a character set, enter it in the individual parts
of the request, as the charset parameter has been removed from the
multipart content-type. |
|
|
|
Fixed an issue with the GraphQL Client Snap that displayed a null pointer exception when the Header authenticated checkbox in the OAuth2 Account is deselected. The Snap now passes the credentials appropriately using URL parameters when the Header authenticated field is deselected. |
|
|
|
Added the API Suite - Google Service Account to the HTTP Client Snap, which enables you to connect to various Google Cloud endpoints such as Analytics 4 and Compute Engine. |
|
|
|
Fixed an issue with the SnapLogic SSL Account for the HTTP Client Snap where a blank keystore or truststore URL caused an error during account configuration. |
|
|
|
Fixed an issue with the HTTP Client Snap that displayed incorrect cookie information, with a null value in the cookies when you have duplicate cookies in the header. The Snap now displays the cookie information correctly. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with the GraphQL Client Snap that caused an error even when the variable value was defined in the previous Snap. |
|
|
|
Fixed an issue with the
HTTP Client
Snap that
caused an intermittent connectivity issue, which resulted in a 404
error . |
|
|
|
Fixed an issue with the HTTP Client Snap where the Snap now conceals the additional authentication headers in the debug information for Secured Headers Account . |
|
|
|
Fixed an issue with the HTTP Client Snap where the validation of the SSL Account for a specified Keystore or Truststore value failed despite providing the correct password. |
|
|
|
Fixed an issue with the
HTTP Client
Snap that
caused pagination to fail when the next Snap in the pipeline could modify the input
document (for example, the Mapper Snap). Note:
Behavior Change: With the |
|
|
|
|
|
|
|
Introduced the GraphQL Client Snap, which enables you to query a GraphQL endpoint and retrieve data. This Snap features a built-in query builder to help you efficiently build queries. |
|
|
|
|
|
|
|
For Snaps using AWS Signature V4 accounts, DNS canonical names are now supported for S3 buckets. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
The HTTP Client Snap does not fail when making a PATCH request containing an empty response body and location in the Headers. The Snap checks the entity length if the response entity is empty and skips the data conversion. |
|
|
|
The
HTTP Client
Snap now accepts the default
value */* for the Accept header, which
communicates to the server that the Snap can handle all forms of response content
types. |
|
|
|
Introduced the API Suite Snap Pack that contains the HTTP Client Snap. This Snap unifies all supported HTTP methods: GET, HEAD, POST, PUT, DELETE, OPTIONS, TRACE, and PATCH that you can execute on a REST API service endpoint. |