Using Github as a code repository for SnapLogic artifacts
Hello SL community!! Coming from a typical SOA/ESB background and working on tools like TIBCO Businessworks, Webmethods, etc. I was wondering if we have a way of using any code repository tool (Github, etc.) to store our Projects and other artifacts. I understand we have a intuitive Import/Export capabilities, this is manual and is a explicit activity to be performed by a developer. I was wondering: if we have anything (or is there a possibility) to integrate SL and GitHub. This should ensure that the Project and its assets gets checked-in into the GitHub repo without us doing any manual import-export. And that this can be further use to move code from one environment to another (code migration). I am new to the SL world, but already finding the community really helpful 🙂 All response would be of help 🙂 Thank you! Sudhendu
Creating a direct link to SnapLogic Manager path
Hello, I am looking for a way to navigate directly to an asset in the Manager view. For instance, if I manually navigate to my Org, Project Space, and Project, the URL looks something like this: https://elastic.snaplogic.com/sl/manager.html?v=[SessionRelatedId]#asset/[Org]/[ProjectSpace]/[Project] If my session is active and I use the “SessionRelatedId” above, loading the page works. However, I cannot give this URL to someone else because they will have a different session. Is there a way to use a static URL to get to a specific asset? Thanks!Rolling back a Snap Pack version
SnapLogic has quarterly Platform and Snap releases. If any of your pipelines stop working due to a new version of a Snap Pack right after a major release, please follow the steps below: Submit a SnapLogic Support ticket. Go to elastic.snaplogic.com Go to Manager → Snap Packs page This page lists the Snaps enabled in your instance of the SnapLogic Elastic Integration Platform, along with their version, type and the number of Snaps they contain. Expand the drop down menu for the Snap Pack which causes the pipeline to fail, and select the previous version. Your pipeline should start executing successfully now. In the meanwhile, the Support team will work with the DEV team to get the issue resolved and eventually ask you to upgrade that Snap Pack to the newer version which the DEV team will upload to your org.