Exporting and importing Playbooks, Custom Integration

if a export a playbook which has versions (v1,v2 ..so on ) and if i export the playbook and import it back the versions is lost , the imported playbook will be the latest version i.e v2.

  1. What is the optimal method for transferring a playbook to a different environment while ensuring version control is maintained?
  2. What is the efficient and best way to move or promote integrations / playbooks / connectors from one environment to another?
  3. Also when we use the export / import method, it will create a copy of the same playbook in the respective environment rather than overwriting? How can we do version control around these developments without creating multiple copies? 
Solved Solved
0 4 651
1 ACCEPTED SOLUTION

I don't think it will

Dev-SOAR, build and push versions to GIT
In Git, merge into new version.x
Prod-SOAR pull new latest versions

If ever you want to roll back, in GIT UI you rollback the version
Prod-SOAR pull new latest versions (which is infact the older one)

View solution in original post

4 REPLIES 4

Sorry to point to the other ticket, but I suggest checking the usage of GIT for version control in your use case. 

Andy

I tried but GITsync only sync lastest version of playbooks/blocks in git

  1. What is the optimal method for transferring a playbook to a different environment while ensuring version control is maintained?

I don't think it will

Dev-SOAR, build and push versions to GIT
In Git, merge into new version.x
Prod-SOAR pull new latest versions

If ever you want to roll back, in GIT UI you rollback the version
Prod-SOAR pull new latest versions (which is infact the older one)

But it still didnt solve the issue .

1) How to maintain Version Control in GCP platform 

if a playbook is duplicated/imported/exported the version of the playbook is lost

i would like to maintain version control