Page Comparison

...

• New Public APIs are added for managing app access and for importing projects.

• Secrets Management:

  • HashiCorp Vault users can use an alternate name for the approle.

  • HashiCorp Vault users can constrain use of secrets by Project Space.

• Create a GitHub tag in Manager.
  

Snaps

• Amazon S3

• API Suite

• Archive, Restore, and Select

• Azure Synapse SQL

• Marketo

• S3 Archive

• S3 Restore

• S3 Select

• Bulk Import and Extract

Studio Patterns

42 new Pipeline Patterns!

Upgrade to this Release

...

• SnapLogic security is enhanced with the recommended OWASP security headers added to responses from a Groundplex:

  • Strict-Transport-Security

  • X-XSS-Protection

  • X-Frame-Options

  • X-Content-Type-Options

  • Content-Security-Policy

  • Referrer-Policy

• The SnapLogic Docker image is updated based on AlmaLinux, instead of CentOS.

• Git Integration enhancements include:

  • The IIP supports creating a GitHub tag. When a branch is checked out for a Project, the Project options menu includes the GitHub Add Tag:

    Image RemovedImage Added

  • When you checkout a Pipeline and commit it without any changes, the order of the Snaps is preserved in the underlying JSON serialization files. This was not the case previously, which caused Pipelines in the GitHub repository to sometimes appear as if they had been updated when they had not.

• On the SnapLogic Dashboard, Pipeline duration is now the completion time minus the Pipeline’s start time.

• Secrets Management enhancements include:

  • To constrain use of secrets by project space, add a project_space property in your secrets-config.json configuration file. Provide the path to the Project Space that contains the secrets. For example, "project_space" : "/snaplogic/shared" constrains users to secrets stored in Accounts in the snaplogic Project Space shared folder.

  • Previously, the SnapLogic secrets-config.json file only supported the approle authentication path. Now, you can use a custom path by adding an auth_path to the secrets-config.json configuration file. For example, the addition of "auth_path": "demo" enables the demo authentication path.

...