Skip to content

v1.7.1

🛡   The Reliability Release

Minimum Supported ThoughtSpot version

Unchanged. ThoughtSpot 10.0.1 and later.

Minimum Supported Python version

Unchanged. Python 3.9.2 and later.

Check out the highlights of our latest CS Tools release!

Real-world ThoughtSpot deployments are large, busy, and always evolving: clusters upgrade, requests time out, networks throttle. This release makes CS Tools resilient to all of it, guided by one principle. When something goes wrong, CS Tools survives it, tells you plainly what happened, and never destroys good data.

searchable metadata now runs to completion even when individual API requests fail. The run skips what it could not fetch and reports exactly which objects are affected.

  • Failure reporting says what was lost and for which objects, naming them rather than dumping GUIDs, and it stays concise even in a failure storm.
  • When an extract is incomplete, the summary points at this run's logfile, which holds a complete named manifest of every affected object, ready to share when you ask for help.
  • TRUNCATE loads protect your data. An incomplete extract is never allowed to replace a complete one. The target is left untouched and the run says so.
  • UPSERT and APPEND loads proceed with partial data. They are additive, so the next successful run fills in the gaps.
  • Fixed the IndexError in searchable deploy that followed a successful import.

scriptability deploy now handles TML attributes newer than the installed TML library, such as viz_style introduced in the 26.x releases. Affected files are skipped and named, and the message identifies the actual cause: the library needs an update, not your files.

scriptability checkpoint warns at export time when a file will not be deployable.

Exit codes reliably reflect the run's outcome, including python -m cs_tools invocations. CI pipelines, this one is for you.

Every phase logs its start, duration, and outcome. Skipped steps say "skipped" and why. A run now explains itself: failures are named rather than counted, and every summary ends with the exact path to a logfile holding the complete record.

  • Duplicate-synonym warnings name the table the column lives in, matching the other column-level warnings.
  • Installation is immune to GitHub API rate limits on shared and corporate networks.
  • Your terminal cursor comes back after a run. Cloud-shell users, rejoice.
  • Clearer messages throughout. Fewer stack traces, more sentences.

One honest footnote: the --verbose flag currently has no effect. The logfile always captures full detail, so you have never needed it. It will become a true live-debug mode or be retired in an upcoming release.

Breaking Changes

None. Every fix in this release ships with tests that pin the behavior.