Does our SnapLogic CI/CD implementation follow best practices?
Hi Everyone, I would appreciate feedback on our SnapLogic CI/CD implementation and whether it aligns with recommended best practices.
We maintain one Azure DevOps Git repository per SnapLogic project.
Multiple branches are used for promotion: feature → dev → uat → main/prod.
Developers create feature branches and corresponding SnapLogic development projects.
Changes are merged through pull requests and promoted across environments via Azure DevOps.
Deployment is fully automated using Azure DevOps YAML pipelines- Using Snaplogic public apis to pull assets (pipelines,files and tasks)
Currently, we use pipeline parameters only and do not use expression files. For environment-specific values, we are considering maintaining separate JSON configuration files in the Git repository, for example: dev.json uat.json prod.json After deployment, the Azure DevOps pipeline would read the appropriate JSON file and update the pipeline/task parameters for the target environment. Question on Task Promotion
Since we are only using pipeline parameters (no expression files), what is the preferred way to handle environment-specific task and pipeline parameter values?
Are there recommended SnapLogic Public APIs for updating pipeline or task parameters during deployment or is the preferred approach to use SnapLogic Metadata/Custom Metadata instead?
Any recommendations or examples from teams implementing automated CI/CD with Azure DevOps would be greatly appreciated.