Symptom: Deploying TML from the /api/rest/2.0/vcs/git/commits/deploy
API endpoint fails when the destination Org is renamed and results in new files being created in the GitHub repository.
Condition: This issue occurs because ThoughtSpot creates mapping files to match GUIDs of source and destination environments. These mapping files use the name of the organization to look up the GUIDs that need to be set on the TML deployed in the destination Org.
Workaround: To work around this issue:
-
Log in to the GitHub account integrated with your ThoughtSpot instance.
-
Navigate to the GitHub repository that stores ThoughtSpot files.
-
Select the branch that stores configuration files.
-
Navigate to the folder ending with
[β¦β].mapping
. -
Check the
.json
file with the old name of your Org. If it exists, delete it: these are the new mappings created after the latest deployment.NoteYou may have to delete the matching files in ThoughtSpot that have been created as part of this deployment operation.
-
Locate the
.json
file with the old name of your Org and rename the file with the new name of the Org.<my_old_org_name>.json
β<my_new_org_name>.json
After you complete these steps, the /api/rest/2.0/vcs/git/commits/deploy
endpoint will use this mapping file and deploy to the destination Org successfully.