SSP Deployer

the ssp deployer connector facilitates the automated import, validation, and deployment of ssp configurations, enhancing the efficiency of security service management the ssp deployer connector bridges swimlane turbine with the ssp (swimlane solution package) deployment process, enabling seamless import, status tracking, and deployment of ssp configurations users can validate ssps through dry runs, track import statuses using unique tracking ids, and upload ssps to specified tenants with options for background processing and entity overwrites this integration streamlines the management of solution packages, significantly reducing manual effort and enhancing operational efficiency within the swimlane ecosystem this connector integrates with swimlane turbine to deploy ssp packages to tenants asset setup or prerequisites to effectively utilize the ssp deployer connector, ensure you have the following prerequisites in place username and password authentication with the following parameters hostname the address of the server where ssp configurations are managed username the user account with permissions to access and manage ssp configurations password the corresponding password for the provided username capabilities this connector provides the following capabilities import ssp retrieve status by tracking id upload ssp notes to access swimlane ssp deploy api documentation link, https //us1 swimlane app/docs configurations swimlane ssp deployer authentication authenticates using username and password configuration parameters parameter description type required url turbine hostname string required username turbine username string required password turbine password string required http proxy optional http/https proxy string optional verify ssl verify ssl certificate boolean optional actions import ssp executes a dry run import of ssp configurations using provided form data to validate the process endpoint url /content/import/try method post input argument name type required description form data object required response data form data file array required swimlane solution content package, ssp form data file file name string required response data form data file file string required response data input example {"form data" {"file" \[{"file name" "test import ssp","file" "test import ssp"}]}} output parameter type description status code number http status code of the response reason string response reason phrase output example {"status code" 200,"response headers" {"content length" "140","content type" "application/json","date" "mon, 19 feb 2023 20 37 23 gmt"},"reason" "ok","json body" {}} retrieve status by tracking id retrieve the current status and results of a content exchange import using a specific tracking id endpoint url /content/import/{{trackingid}}/status method get input argument name type required description path parameters trackingid string required tracking id of the import process input example {"path parameters" {"trackingid" "aehniq9suh6xoewua"}} output parameter type description status code number http status code of the response reason string response reason phrase entities object output field entities entities additionalprop1 array output field entities additionalprop1 entities additionalprop1 uid string unique identifier entities additionalprop1 version number output field entities additionalprop1 version entities additionalprop1 id string unique identifier entities additionalprop1 name string name of the resource entities additionalprop1 disabled boolean output field entities additionalprop1 disabled entities additionalprop2 array output field entities additionalprop2 entities additionalprop2 uid string unique identifier entities additionalprop2 version number output field entities additionalprop2 version entities additionalprop2 id string unique identifier entities additionalprop2 name string name of the resource entities additionalprop2 disabled boolean output field entities additionalprop2 disabled entities additionalprop3 array output field entities additionalprop3 entities additionalprop3 uid string unique identifier entities additionalprop3 version number output field entities additionalprop3 version entities additionalprop3 id string unique identifier entities additionalprop3 name string name of the resource entities additionalprop3 disabled boolean output field entities additionalprop3 disabled issues object output field issues issues additionalprop1 array output field issues additionalprop1 issues additionalprop1 errorcode number error message if any issues additionalprop1 message string response message output example {"status code" 200,"response headers" {"content length" "140","content type" "application/json","date" "mon, 19 feb 2023 20 37 23 gmt"},"reason" "ok","json body" {"entities" {"additionalprop1" \[],"additionalprop2" \[],"additionalprop3" \[]},"issues" {"additionalprop1" \[],"additionalprop2" \[],"additionalprop3" \[]},"errors" {"additionalprop1" \[],"additionalprop2" \[],"additionalprop3" \[]},"createddate" "string","modifieddate" "string","createdbyuser" {"id" "string","name" "string"},"modifiedbyuser" { upload ssp upload and deploy ssp packages to specified tenants, requiring attachments, account, tenant, and entity ids input argument name type required description attachments array required swimlane solution content package, ssp attachments file name string required name of the resource attachments file string required parameter for upload ssp account string required count value tenant string required parameter for upload ssp overwrite string optional determines if import process overwrites existing entities defaults to false background string optional determines if import process should run as a background task defaults to true entity ids array required ids of the entities in the ssp which should be imported input example {"attachments" \[{"file name" "test import ssp","file" "test import ssp"}],"overwrite" "true","background" "true"} output parameter type description results string result of the operation output example {"results" "\\"aehniq9suh6xoewua\\""} response headers header description example content length the length of the response body in bytes 140 content type the media type of the resource application/json date the date and time at which the message was originated mon, 19 feb 2023 20 37 23 gmt