Is your feature request related to a problem?
Yes, when running commands, we always check for updates by calling the GitHub API. When running many commands in a short time (e.g. devspace status sync), we are hitting the GitHub API rate limit and see this error:
[WARN] Couldn't check for newest version: GET https://api.github.com/repos/covexo/devspace/releases: 403 API rate limit exceeded for 178.5.106.180. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.) [rate reset in 8m47s]
Which solution do you suggest?
I suggest running an update service that does the GitHub API request regularly and caches the latest release. When checking for updates, the request should be made against the update service instead of against the GitHub API directly.
Which alternative solutions exist?
Alternatively, we could ask the user for a personal access token for the GitHub API but that would require additional configuration and force users to have a GitHub account.
Additional context
/kind feature
Is your feature request related to a problem?
Yes, when running commands, we always check for updates by calling the GitHub API. When running many commands in a short time (e.g. devspace status sync), we are hitting the GitHub API rate limit and see this error:
Which solution do you suggest?
I suggest running an update service that does the GitHub API request regularly and caches the latest release. When checking for updates, the request should be made against the update service instead of against the GitHub API directly.
Which alternative solutions exist?
Alternatively, we could ask the user for a personal access token for the GitHub API but that would require additional configuration and force users to have a GitHub account.
Additional context
/kind feature