ThoughtSpot Git Integration Issue

Yes. The API should be run on the org where the objects need to be deployed. It will read the objects from the branch specified and deploy the objects in the org where API is being run.
10 Replies
Leon
Leon12mo ago
@Anand @Sandeep I see. I am still having some trouble though. In the first screenshot I have the config of the main branch (one of the branches is prod but that shouldn't be there, I can't remove it but I don't think it affects the result?) In the second screenshot, when I try to do Deploy Commit without a commit_id specified, it says "Requested branch not configured.Exception:Ref main-org-0 cannot be resolved". When I do specify the commit_id, it will say it was successful but the changes aren't in ThoughtSpot. Do you have any ideas on why this could be? I can provide more information if needed. Thanks!
No description
No description
Sandeep
Sandeep12mo ago
@Anand : Could you please help here
Anand
AnandOP12mo ago
@Leon I believe the configuration is not done correctly for all the orgs. Can you help with these details Source/dev org - corresponding branch where objects will be committed Target/prod org - corresponding branch from where where objects will be deployed I'll provide details on how to configure, commit and deploy across these orgs.
Leon
Leon12mo ago
@Anand Source/dev org - dev branch
No description
Leon
Leon12mo ago
Target/prod org - main branch ("prod" branch shouldn't be there but can't delete or update it but hopefully that doesn't affect anything)
No description
Leon
Leon12mo ago
I can commit changes which goes into GitHub but yeah there possibly could be something I missed in the configuration.
Leon
Leon12mo ago
Another question: is the "Develop" tab supposed to be available for other orgs too? In my non-primary orgs, I do not have it - I only have it in my primary org. I do not know if this is supposed to be the way it is or if it needs to get enabled.
No description
Leon
Leon12mo ago
Hi @Anand @Sandeep I was wondering if there was any update on this. Thanks!
Anand
AnandOP12mo ago
Hi @Leon Apologies. Missed your messages. @Sandeep Can you help with "Another question: is the "Develop" tab supposed to be available for other orgs too? In my non-primary orgs, I do not have it - I only have it in my primary org. I do not know if this is supposed to be the way it is or if it needs to get enabled." @Leon The update config API only adds new branches. To remove the unwanted branch, you would need to delete the config in the "Fake Prod" branch and create it with the branches required. @Leon Your config looks good now. You should run deploy API from the "Fake Prod" org context to ensure it picks the configuration of that org. With that it should pick the branch correctly and deploy. I think the org context of the user is probably incorrect due to which it does not pick the branch correctly.
Sandeep
Sandeep12mo ago
@Leon : To enable the develop tabs in non-primary org, could you please raise the support case

Did you find this page helpful?