Snap Pack history: Binary
|
|
|
Updates |
|---|---|---|---|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed the private key validation issue for ECDSA keys in SSH Auth Account . |
|
|
|
Fixed an issue with the File Poller Snap that failed after upgrading to the 4.42 (main31019) version. The issue has been addressed by removing the multi-thread implementation. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
|
|
|
|
|
|
|
|
Enhanced the Private key and Public key fields in the Private Key Account to support expressions. |
|
|
|
Upgraded the SMB client library to v2.6.1 to address connection issues. |
|
|
|
Enhanced the following Snaps to support Azure Data Lake Gen2 OAuth2 Account using ABFS (Azure Blob File System) and ABFSS (Azure Blob File System Secure) protocols: |
|
|
|
|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
|
|
|
|
Upgraded the org.json.json library from v20090211 to
v20240303, which is fully backward compatible. |
|
|
|
Enhanced the Azure Storage Account with Managed Identity, which provides applications with an automatically managed identity for connecting to resources that support Microsoft Entra ID authentication. |
|
|
|
Fixed an issue with the File Poller Snap where the Snap applied a case-sensitive filter in the Windows operating system. |
|
|
|
Enhanced the Decompress Snap to support encrypted and unencrypted ZIP and 7z files through the new File Password Account type. |
|
|
|
The Azure Data Lake Account has been removed from the Binary Snap Pack because Microsoft retired the Azure Data Lake Storage Gen1 protocol on February 29, 2024. We recommend replacing your existing Azure Data Lake Account with other Azure Accounts. |
|
|
|
Fixed an SMB (server message block) connectivity issue within the Binary Snap Pack , as the incorrect name provided by the SMB client did not match the Windows cluster virtual name, affecting the SPN (service principal name) connection. |
|
|
|
Fixed a configuration exception for a null value. |
|
|
|
Fixed an issue with the
File Writer
Snap, which partially writes the file for some FTPS servers by pausing for seconds
before closing the output stream as specified in the global property
ftpsDelayBeforeClosing. |
|
|
|
Fixed an issue with the
File Poller
Snap that displayed an exception when an unauthorized character ':'
was used in the Windows Snaplex. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with the File Poller Snap that caused it to poll recursively for files in the root directory of the S3 bucket. |
|
|
|
Fixed an issue with the Binary Snaps that failed to build a data connection when connecting to the FTP server over FTPS protocol. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with the File Operation Snap (SFTP protocol) where the error message did not display during a move operation, although the existing file was available in the target path and the Error if exists checkbox was selected. |
|
|
|
Fixed an issue that occurred when node properties were used to override default algorithm specifications for SFTP operations. |
|
|
|
Fixed an issue that caused account credentials to be visible in the stack trace of some failed SFTP operations. |
|
|
|
Fixed an issue that caused NTLM authentication issues when trying to access SMB servers. |
|
|
|
The JSON key field in the Binary Google Service Account supports JSON strings. You can upload the JSON key either from SLDB or dynamically pass the value using a pipeline parameter or access values from Secrets Manager. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
|
|
|
|
|
|
|
|
Added the PGP Sign Snap, which allows binary data to be signed using PGP. |
|
|
|
With the 4.33 GA release, support for some algorithms for SFTP connection
negotiation is removed for improved security and because we’ve updated the library
used to connect to SFTP sources. With Snap Pack version
433patches21645, you can modify the global properties. Refer to
the Configuration Settings for Snaps
documentation for details about how to revert to the previous settings. |
|
|
|
Fixed the issues with the AES Encrypt and AES Decrypt Snaps, where the Snaps previously did not include the error stack trace in the error view. The Snaps now provide detailed information in case of any issues or errors. |
|
|
|
Warning: Starting from version 433patches21482, the
PGP Encrypt
Snap will no longer support
encryption with an expired key. To ensure continued support for encryption, we
highly recommend extending the expiration of your PGP key.
|
|
|
|
Fixed an issue with the
Multi File Reader
Snap where it failed with
the error S3 object not found when the Snap found no matching file
to read and the Folder/File property value did not end with a forward slash
(/). |
|
|
|
|
|
|
|
The Key passphrase field in the Private Key Account now supports expressions, allowing dynamic evaluation using pipeline parameters when the expression button is enabled. |
|
|
|
Fixed an issue where the Zipfile Read and Zipfile Write Write Snaps failed to display the input schema for the File or File name field when using an expression. |
|
|
|
|
|
|
|
The JSCH library has been upgraded to version 0.2.7. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
The PGP Decrypt Snap now allows you to skip the signature verification when you face an issue with the signature in the encrypted file. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
|
|
|
|
Fixed an issue with the Directory Browser Snap, which failed with a null
pointer exception error when connecting to the SFTP server containing a port
number. Note: The
Binary Snap Pack
is deployed
as both the latest and stable distribution. We recommend that you use this version
for your Org when using the recommended Snaplex version (main-13269 - 4.30
GA). |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Enhanced the following Snaps and Accounts that use SnapLogic File System (SLFS) to display Lint warnings in Pipelines when using incorrect file paths to read and write files. We recommend that you use the File Upload :Upload_icon: icon to specify the file path. |
|
|
|
|
|
|
|
Fixed an issue in the
File Writer
,
S3 File Writer
, and
Zipfile Write
Snaps where the Snaps failed
with AccessControlListNotSupported error when using an external AWS
account to write to the bucket if it has the bucket-owner-enforced
setting enabled. With this fix, you can select the None option (the default
value), from the AWS Canned ACL dropdown list, indicating that no Canned ACL
request is set when writing a new file to prevent the error. |
|
|
|
|
|
|
|
|
|
|
|
Fixed an issue with the SMB Account where the Snaps could not re-establish a lost connection to the SMB mount point. |
|
|
|
|
|
|
|
Fixed a memory leak issue when using HDFS protocol in Binary Snaps. |
|
|
|
Fixed an issue with the File Writer , where the Snap failed to open a channel while accessing through a SFTP protocol. |
|
|
|
|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
|
|
|
|
|
|
|
|
Fixed an issue with the
PGP Decrypt
Snap where the Snap writes an empty document to the output view when there is an
error in the Snap. It will now decrypt the document and write it to the output view
only if it succeeds. Warning: As of 23 Jun 2021 we have discovered an
issue with this Binary patch affecting the PGP Decrypt Snap. In case your
Pipelines use the PGP Decrypt Snap, we recommend you to NOT use this patch. Else,
your Pipelines will likely fail. We're working on a fix and will be deploying a
Snap patch soon. |
|
|
|
Enhanced the SFTP session in Binary Snaps to support the SFTP servers which close SFTP sessions slowly. |
|
|
|
Enhanced the
S3 File Writer
Snap with
an ability to write S3objects with Access Control List (ACL) details in a single API
call. Note: In the 4.23 release, the S3 File Writer Snap used to write an S3 file
and then set ACL if the ACL property was not empty. If the file write was
successful and the ACL setting failed, both the output document in the output view
and the error document in the error view was displayed. This issue has been
resolved in the 4.24 release by enabling the Snap to configure ACL while writing
the file. Therefore, the Snap produces an error document in the error view if the
ACL configuration fails, irrespective of whether the file write action passes or
fails. |
|
|
|
Enhanced the S3 File Writer to use an MD5 checksum that automatically checks for data integrity and corruption while uploading the file. |
|
|
|
Fixed the file operation error of copying large S3 files in the File Operation Snap by supporting the transfer of zero-byte S3 files while uploading a file. |
|
|
|
|
|
|
|
Upgraded with the latest SnapLogic Platform release. |
) for
the following fields that allow the use of Pipeline parameters to populate the properties.