SnapLogic release process
Overview
SnapLogic customers can keep their current Snaplex and Snap Packs for up to four weeks and two days after each quarterly release. This period is mainly for testing and ensuring the stability and functionality of the new Snaplex and Snap Packs before deploying them to all environments (Orgs).
You can update Snaplex instances within an environment (Org) automatically by selecting the checkbox on . This setting updates the Snaplex to the latest available version.
This new release process has the following combinations:
| Control Plane, User Interface | Snaplex | Snap Packs | Supports Configuration? |
|---|---|---|---|
| Updated | Old | Old | Yes. It supports both the Stable and Latest versions of older Snap Packs running on an older Snaplex. Additionally, it supports Snap Pack overrides. |
| New | No. New Snap Packs require new Snaplex. | ||
| New | Old | No. Old Snap Packs don't run on a new Snaplex. If an issue is found with a new Snap Pack, it can be overridden with an older version in consultation with SnapLogic Support. | |
| New | Yes. It supports both the Stable and Latest versions of older Snap Packs running on an older Snaplex. Additionally, it supports Snap Pack overrides. |
The quarterly release of the SnapLogic platform ensures zero downtime. This means you won't encounter any maintenance notices on the SnapLogic UI. You can seamlessly access the UI during the maintenance window and make updates without interruption. Your pipelines, API calls, and Scheduled Tasks will continue to operate as usual.
Snaplex and Snap Pack upgrades automatically occur four weeks plus two days after a quarterly release. Older Snaplex nodes and Snap Packs are automatically updated and Snaplex rollbacks aren't allowed. You can see the warning messages before the grace period ends.
If you don't select the checkbox in , then the system suspends the automatic updates for Snaplex nodes and doesn't change the version. During this grace period, you can manually upgrade the new Snaplex Web Application Resource (WAR) file to test your pipelines if they're working as expected. You can then try out the new Snaps and Snap Packs.
- All nodes within a Snaplex must be configured to run the same Snaplex version and Snap Pack versions.
- The Snap Catalog will continue to show older versions of Snap Packs until all JCC nodes within an organization are upgraded to the new version. Premium Snap Packs that are newly published won't be accessible in the Snap Catalog until all JCC nodes are upgraded. During pipeline execution, the appropriate Snap Pack will be utilized depending on whether the JCC nodes has been upgraded or not.
- Private Snap Packs can be used regardless of the JCC version.
To upgrade automatically to the latest available version, select the checkbox in .
The settings you configure on the page determine which Snap Packs are utilized during pipeline execution. As an administrator, you can choose the options that align with the needs of your organization or project. For instance, you could configure a developer environment (org) to have the latest Snap Packs for testing new features. For a production environment (org), opting for Stable Snap Packs ensures smooth operation and expected functionality.
- New: This option shows Snap Pack choices (Latest or Stable) for an updated Snaplex.
- Old: This option shows Snap Pack choices (Latest or Stable) for an older Snaplex.
You can use this menu to test the new Snaplex version and Snap Packs independently from the older Snaplex and Snap Packs.
- Latest: The most recent set of Snap Packs.
- Stable: The most stable set of Snap Packs (as recommended by SnapLogic).
The Snap Packs used in a pipeline can vary depending on your configuration.
In addition to the menu choices (Latest/Stable, Old/New), you can also configure individual Snap Pack local overrides to use when a pipeline runs. For example, you might have a Stable set of Snap Packs configured for your environment. However, you can select a later (or earlier) version for a few Snap Packs, depending on your needs. Sometimes, instead of the Latest or Stable Snap Pack, you may have a local override set for one or more Snap Packs. These local settings are stored until you update the Snap Packs. Once you update the Snap Pack, you will need to re-apply the local overrides.
Snap Pack Distribution Rules
Snap Packs are tied to Snaplex versions. Following rules apply in the Snap Pack distribution:
- If you are running an older Snaplex, a Stable distribution refers to the old Snap Packs in Stable.
- Overriding a Snap Pack to point to a next release version is not recommended, but will not be disabled.
- If you are running a new Snaplex, a Stable distribution refers to the new Snap Packs in Stable.
- Rolling back from a new Snaplex to an old Snaplex will switch to using older, Stable Snap Packs. The local Snap Pack overrides you applied before the upgrade are restored.
- When a Dot Release is available for a Snap Pack, the Snap Pack is published and the Latest distribution points to the new Snap Pack.
- Only environments (Orgs) configured for a Latest distribution with a new Snaplex will automatically receive the Snap Pack change. If you have environment (Org) configured for a Stable distribution and a new Snaplex, you can manually apply a local Snap Pack override to use the new Snap Pack.
- Customers who need a Snap Pack patch must upgrade to the latest Snaplex to get the change. Using new a Snap Pack Dot Release with an old Snaplex is not supported.