-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Is there an option to disable this caching output to stdout while accessing SDK #184
Comments
@gopurx There's is no exposed option today to simply disable the stdout. Zscaler DevRel |
Every time an SDK is referred, we are getting this trace of line which is not of use as much. It would be easy if there is an option to disable this or redirect to a file. "2024-10-11 10:06:45,115 - WARNING - Saving to cache. |
Ok as I said this is only shown if you're running the SDK in debug mode, which we do not recommend. |
To confirm, we are not running with debug mode enabled. These messages in STDOUT stream are still being displayed constantly.
From: William Guilherme ***@***.***>
Date: Tuesday, October 15, 2024 at 4:26 AM
To: zscaler/zscaler-sdk-python ***@***.***>
Cc: Gopu, Revanth ***@***.***>, Mention ***@***.***>
Subject: Re: [zscaler/zscaler-sdk-python] [FEATURE] Is there an option to disable this caching output to stdout while accessing SDK (Issue #184)
Ok as I said this is only shown if you're running the SDK in debug mode, which we do not recommend.
We will implement an option to explicitly disable logging in the future.
—
Reply to this email directly, view it on GitHub<#184 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJHQUMKIAWZOMENUOQYHDQTZ3TNVPAVCNFSM6AAAAABPZBS3ZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJTGM3DOMRYGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Problem Statement
Is there an option to disable this caching output to stdout while accessing SDK
WARNING - Saving to cache.
Proposed Solution
option to disable this echo, as this could be noisy during automation and invoking 10s of methods for 100s of resources
Additional Context
Add any other context, references or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: