Skip to content

Fix/console log policy plugins - #353

Draft
shafeeqd959 wants to merge 3 commits into
developmentfrom
fix/console-log-policy-plugins
Draft

Fix/console log policy plugins#353
shafeeqd959 wants to merge 3 commits into
developmentfrom
fix/console-log-policy-plugins

Conversation

@shafeeqd959

Copy link
Copy Markdown
Contributor

No description provided.

Your Name added 3 commits August 18, 2026 20:05
Step 2 of the logger-scoping change; step 1 landed in the cli repo
(console-policy module, logger filter, progress-manager self-seeding,
console-policy init hook).

Console visibility is now a process-wide policy resolved once, before
any command runs, from static inputs: CS_CLI_CONSOLE_LOGS, then user
config (on `true` only), then the plugin's csdxConfig.showConsoleLogs,
then files-only. Plugins no longer decide it, thread it, or persist it.

- Remove the log.progressSupportedModule writes and the
  clearProgressModuleSetting calls; nothing reads that key any more.
- Drop the seeding boilerplate at all 17 progress-manager call sites —
  CLIProgressManager reads the policy itself, so createSimple/
  createNested no longer take showConsoleLogs.
- Reduce the local withLoadingSpinner wrappers to a plain delegation;
  the manager now skips the spinner in console-log mode internally.
- Re-source the sites that choose their own content (audit's banners,
  the `if (!showConsoleLogs) cliux.print` compensation in export,
  import and import-setup) to isConsoleLogEnabled().
- Stop audit persisting `log.showConsoleLogs: false` into the user's
  config. That value silently outranked every plugin declaration; step
  1 makes a persisted `false` read as "no opinion", and the two halves
  have to ship together.
- Declare csdxConfig.showConsoleLogs on query-export and cli-tsgen,
  whose only user-facing output is log.*.

Console logs and the progress UI are mutually exclusive: opting in to
console logs turns the bars, spinners and headers off, so the two
consumers of the terminal can never interleave.
@snyk-io

snyk-io Bot commented Aug 19, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@github-actions

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 0 25 ✅ Passed
🟡 Medium Severity 0 0 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

✅ BUILD PASSED - All security checks passed

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