Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel1
outlinefalse
typeflat
printablefalse

...

Snap Pack

Date

Snap Pack Version

Updates

LLM Utilities

438patches28597

Added the Message Appender Snap to the LLM Utilities Snap Pack that enables you to merge document streams into a single output stream.

Flow

438patches28470

Added the PipeLoop Snap that enables you to loop on pipeline executions based on a stop condition or iteration limit. The execution workflow of this Snap enables the parent pipeline to control and manage iterative processes using the child pipeline, for scenarios where repeated processing is needed until a specific stop condition is met.

API Suite

438patches28567

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.

JDBC

438patches28541

The JDBC Snap Pack version 438patches28052, which removed the default bundled Oracle and Redshift drivers (JAR files), is now rolled back with 438patches28541. Now, the drivers are bundled by default with the Oracle and Redshift Snap Packs. This rollback might cause a connectivity issue when connecting the JDBC Snaps to the Sybase database using the jConnect Driver. Based on your use case requirements, follow the below steps:

  • To manually upload the custom Oracle or Redshift JDBC driver in the JDBC Database account, you must use the 438patches28052 Snap Pack version.

  • To use the bundled Oracle and Redshift drivers, you must use the latest JDBC Snap Pack version 438patches28541.

Sharepoint Online

Microsoft OneDrive

438patches28439

Updated the Kotlin library for SharePoint Online and Microsoft OneDrive Snap Packs with the okhttp library Platform version to avoid Kotlin library dependency conflict.

Salesforce

438patches28607

Fixed an issue with the Salesforce Publisher Snap where an invalid session triggered infinite retries, resulting in many open file descriptors that eventually crashed the node.

...

Important update from Snowflake about the Security Policies:

Snowflake recently signed the Cybersecurity and Infrastructure Security Agency (CISA) Secure By Design Pledge. In line with CISA’s Secure By Design principles, Snowflake recently announced several security enhancements in their platform — most notably the general availability of Trust Center and a new Multi-Factor Authentication (MFA) policy.

Effective October 2024, MFA will be enforced by default for all human users in any new Snowflake account. Service users (accounts designed for service-to-service communication) will not be subject to this MFA requirement.

Basic Authentication accounts:

If you currently use the Basic authentication to access Snowflake, we recommend one of the following:

  • Update your password to a maximum of 14 characters and a minimum of 8, and ensure it does not match any of the previous five passwords. Learn more.

  • Migrate to Key-Pair authentication: This method involves generating a public and private key pair, where the private key is securely stored and the public key is registered with your Snowflake account.

  • Migrate to OAuth2 authentication: This is a widely adopted standard for secure delegated access. It allows applications to obtain limited access to user accounts on an HTTP service, facilitating safer and more manageable authentication flows.

Implementing the above recommendations will secure your data and protect sensitive data, ensuring compliance with Snowflake's updated security policies. Learn more. For questions, contact support@snaplogic.com.

Upcoming

JDBC Snap Pack:

The JOOQ library will be upgraded from v3.9.1 to v3.17.x  as the Latest release (following the November GA). Pipelines using the Generic - JDBC Snaps might be impacted by the jOOQ upgrade because the latest jOOQ version is not fully backward-compatible.

...