Posting on behalf of Bhavin to Internal Only
With 4.9 release we now have a new API to migrate projects from one org to another as long as user is added to source as well as target orgs (obviously)
API Detail:
Syntax = https://elastic.snaplogic.com:443/api/1/rest/public/project/migrate/ORG/SPACE/PROJECT
Authorization Header = Basic Auth, pass on your Snaplogic uname/pwd
Body = application/json
Example:
https://elastic.snaplogic.com:443/api/1/rest/public/project/migrate/ConnectFasterInc/BK/DEV
{
"dest_path":"/tacobell/projects/bk",
"asset_types":["File","Job","Account","Pipeline"],
"async":"true",
"duplicate_check":"false"
}
Response:
{
โresponse_mapโ: {
โstatus_tokenโ: โ6e6600cd-2992-4423-95c3-ffb94293a3bdโ,
โstatus_urlโ: โhttp://elastic.snaplogic.com/api/1/rest/public/project/migrate/6e6600cd-2992-4423-95c3-ffb94293a3bdโ
},
โhttp_status_codeโ: 200
}
This runs as an async call and will migrate (copy) everything from ConnecFasterInc/BK/DEV to /tacobell/projects/bk, you can check status of the migration by visiting status_url
If a project already exists and duplicate_check set to false will create another project with the same name appended by (NUMBER) ex: if bk already exists inside /tacobell/projects then subsequent runs will add bk(1), bk(2) and so on, I wish we had an โoverwriteโ or โmergeโ parameter option but neverthless this is much easier than META snaps (IMO).
