You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the civo CLI (especially while testing script) causes a lot of version checks to the GitHub API when the VersionCheck method is called from various places.
I'd like a configuration option to disable the version check.
I've forked the repo and want to start working on this, and would appreciate guidance on how the config file is modified and consumed.
So far, I've got a working version that adds a condition to the statement to determine whether the version check should be called.
The text was updated successfully, but these errors were encountered:
I saw that line of code, but that doesn't seem to be the case for me. Perhaps I'm doing something unexpected by calling the civo CLI from within a bash script?
What I'm seeing is that GH is throttling my calls after a few runs of my script.
Upon looking closer at the code, I think I might be looking in the wrong place. The CivoAPIClient function callscommon.VersionCheck() without any condition on whether it should be making that call to the GitHub API. Do you think this might be the cause?
Using the
civo
CLI (especially while testing script) causes a lot of version checks to the GitHub API when the VersionCheck method is called from various places.I'd like a configuration option to disable the version check.
I've forked the repo and want to start working on this, and would appreciate guidance on how the config file is modified and consumed.
So far, I've got a working version that adds a condition to the statement to determine whether the version check should be called.
The text was updated successfully, but these errors were encountered: