Programmatically get SLPROPZ contents and write to a file
Within a pipeline, how can I programmatically access the SLPROPZ file for a snaplex, and write the contents of the file out to the local hard drive? We have over 500 snaplexes that we need to do this for, so manually downloading them all is not a good solution. Also, for various reasons I won’t go into, we cannot employ an outside task that just pings each download endpoint. This HAS to be done from within a set of pipelines. The SnapLogic Metadata snaps give me the ability to list Snaplexes and to read them as a set of JSON attributes. But there seems no way to obtain (or reconstruct) the SLPROPZ file. Any help that can be provided will be much appreciated!Dynamically setup dashboard execution label from triggered task
Hi Snaplogic Gurus, Good day, is there a way to set the execution label using triggered task FYI, the executing pipeline that I would like to dynamically set the execution label is the parent pipeline this is a common pipeline then accepts a JSON object and routes to different child pipeline, is there maybe a header, attributes or key/value pair that can be set in the PUT request body that is hidden that I can use? I tried updating the path, name, label of the pipeline asset using update snaplogic snap but it just created a new one, I had that idea since triggered task are not mapped by pipeline name but snodeid I’m trying to output something like this in the dashboard Thanks, EmEmPipeline Directory Generator
Created by Chris Ward, SnapLogic This pipeline generates a Google Sheet containing key information relating to all Pipelines within a customers org. This allows customers to maintain both a consolidated & up to date view of all Pipelines within a specific Org alongside its last run status and other important metadata. The Pipeline would need to be scheduled to run on a set cadence. The pattern could be further adapted to write the output to an alternative destination or even consumed externally as an API. Configuration The following pipeline parameters can be used to configure certain aspects of the Pipeline. OrgName GoogleSheetName GoogleWorksheetName Sources: SnapLogic API & Metadata Snaps Targets: Google Sheets Snaps used: SnapLogic Metadata, REST Get, JSON Splitter, Mapper, Join, Sort, Google Sheets Worksheet Writer Downloads Pipeline Directory Generator.slp (19.7 KB)Migration Patterns
The following patterns migrate assets from one project to another in the same org. These patterns make use of the SnapLogic Metadata Snaps. Source: Existing accounts, files, and pipelines within SnapLogic Target: A second project within SnapLogic Snaps used: SnapLogic Metadata Snaps, Mapper, Requirements You must have access to both projects. You will need to define the following pipeline parameters: source_path, in the form of /orgname/projectspace/project target_path, in the form of /orgname/projectspace/project Migrate Accounts The SnapLogic List Snap gathers the list of accounts in the specified source_path parameter. The SnapLogic Read Snap reads the incoming $path for the accounts. The Mapper Snap maps the target path. The SnapLogic Create Snap writes the accounts to the target location. Migrate Files The SnapLogic List Snap gathers the list of files in the specified source_path parameter. The Mapper Snap maps the source path to a $source_path field for use in the Read Snap. The SnapLogic Read Snap reads the incoming $path for the files. The SnapLogic Create Snap writes the files to the target location. Migrate Pipelines The SnapLogic List Snap gathers the list of pipelines in the specified source_path parameter. The SnapLogic Read Snap reads the incoming $path for the pipelines. The Mapper Snap maps the target path. The SnapLogic Create Snap writes the pipelines to the target location. Pipeline Downloads Migrate Accounts.slp (5.7 KB) Migrate Files.slp (6.0 KB) Migrate Pipelines.slp (5.7 KB)
