euporphium
06/18/2026, 5:50 PMAnswer Overflow
06/18/2026, 5:50 PMspotter-code
06/18/2026, 5:50 PMtype values shown are:
- LIVEBOARD
- ANSWER
- LOGICAL_TABLE
- CUSTOM_ACTION
(No FEEDBACK type is listed.)
- So if Spotter coaching FEEDBACK is not appearing in Git integration or VCS endpoints, that likely means it is not currently versioned as a supported metadata type through those APIs.
- For your deletion concern: use Git commit with delete_aware (defaults to true) so files are removed from the repo when they no longer exist in ThoughtSpot. This addresses repo drift, but only for supported metadata types.
Practically, your current approach (export/import TML) is valid, but it won’t automatically clean up deleted objects in target unless you add an explicit cleanup step (or use VCS deploy flows where delete-awareness is supported for those object types).
Suggestions:
- Treat Spotter coaching/feedback as a separate promotion stream from TML/VCS until FEEDBACK appears as a supported metadata type in official endpoints.
- For now, build a promotion runbook:
1. Export/import supported objects (Liveboards, Answers, etc.)
2. Run a reconciliation step for removals (manual/scripted)
3. Re-apply Spotter coaching config/content manually (or via any dedicated future endpoint if/when added)
- If you want, I can help you design a safe “diff + cleanup” workflow for non-delete-aware TML migrations between envs.
Docs:
- Git integration overview: https://developers.thoughtspot.com/docs/git-integration
- REST API v2 overview: https://developers.thoughtspot.com/docs/rest-api-v2
- REST API playground: https://try-everywhere.thoughtspot.cloud/v2/#/everywhere/api/rest/playgroundV2_0Swarnika
07/01/2026, 7:01 PM