Skip to content

fix: stabilize secrets scanner runs - #405

Open
hurcy wants to merge 1 commit into
databricks-industry-solutions:Release/0.10.0from
hurcy:bugfix/secrets-scanner-stability
Open

hurcy wants to merge 1 commit into
databricks-industry-solutions:Release/0.10.0from
hurcy:bugfix/secrets-scanner-stability

Conversation

@hurcy

@hurcy hurcy commented Sep 14, 2026

Copy link
Copy Markdown

Summary

  • Avoid no-op Delta table and column comment writes during SAT initialization, preventing concurrent metadata conflicts.
  • Run notebook and cluster secret scans sequentially within a workspace on serverless compute.
  • Exclude compiled Python cache artifacts from source scanning and record genuine materialization coverage gaps in a dedicated Delta table.
  • Include child scan details in the driver failure message.

Fixes #391.

Validation

  • python3 -m py_compile passed for all modified notebooks.
  • git diff --check passed.
  • codespell passed on staged files.
  • Validated against a Databricks serverless workspace: Secrets Scanner completed successfully with zero coverage gaps after excluding __pycache__ .pyc files.

Test note

pytest tests/ requires an external config file containing a MEISTERSTUFF section. In a clean checkout it collected 193 tests but 192 stopped at fixture setup because /path/to/config.txt was absent; this is unrelated to the modified notebook code.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants