SnapLogic_CICD_With_GitHub.pdf

Automated Deployment (CICD) of SnapLogic assets with GitHub

Introduction 2

SnapLogic Git Integration 3

Git model 3

A) Asset deployment across environments - an example 3

New / Modified Assets in the Dev Environment 4

Prod Environment 4

Workflow execution 14

Table 2.0 - Steps for subsequent / future asset deployment 16

Deployment flow (Dev->Test->Prod) 16

Deployment flow: Dev->Test->Prod 16

Introduction

This guide is a reference document for the deployment of SnapLogic assets to a GitHub repository. It

also includes sample YAML code for a GitHub Actions workflow which can be used to automate the

deployment of assets across Environments (Dev -> Stg / Stg -> Prod, etc.)

SnapLogic Git Integration

Git Integration allows you to track, update, and manage versions of SnapLogic assets using the

graphical interface or the public APIs. The following asset types can be tracked in a GitHub

repository:

Git operations

The assets in this example are tracked at a project space level, i.e. one Project Space in Dev is

associated with a single branch in the GitHub repository. A single GitHub repository is used to

maintain the branches for Dev, Stg, Prod, etc. Repository branches can also be deleted and

re-created for specific deployment needs.

Project Space: Dev_Integration_Space with the below project folders having SnapLogic assets.

We have already defined an empty project space named Prod_GH_Integration in the Prod env. This