Git workflow for a single developer

How one developer tracks SnapLogic assets with a Git repository.

One developer needs only one branch at a time. Create a branch from the main branch, commit the work, open a pull request, merge it, and tag the release. For the branching model these steps follow, refer to Git workflow and branching model.

Steps related to the SnapLogic project include links to detailed steps and to the APIs for automation:
  1. Create a repository in your Git environment.
  2. To optionally use a secrets manager, set up credentials in the vault. Use your environment name in the keys to separate development from production accounts.
  3. In the sandbox SnapLogic environment, set up your endpoint accounts:
  4. In a project space, create one or more projects to associate with the Git repository.
  5. Use the SnapLogic Git Integration to create a repository branch and check it out for a Project Space or a project.
  6. Design and develop your pipelines and tasks.
  7. Commit the changes.
  8. Create a pull request for review.
  9. When finished with review, merge the pull request branch to the main branch in your Git provider.
  10. Check out the main branch for the Project Space or project where you created the branch. A tag marks the commit that the Project Space or project tracks, so without this step the tag marks the feature branch instead of the merged commit. Refer to Checkout a branch or tag.
  11. Associate a tag with the latest files in the main branch.
  12. In the production environment, perform a pull using the defined tag. Accounts with the same name across all Orgs are considered the same account.

To undo, perform a pull using a tag defined for an earlier version of the main branch files.

To automate delivery, set up a CI/CD workflow in your Git provider that's automatically triggered on update of the main branch. The CI/CD workflow pulls the updated files into the production environment.