[Telemetry] Implement local caching to persistently store user config. Remove Firestore dependency completely#5594
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request transitions the telemetry configuration and metadata management from a remote Firestore dependency to a local file-based caching mechanism. This change enhances the robustness of the CLI by removing reliance on external database services for core functionality, ensuring consistent behavior across different environments and improving performance by reducing network overhead. Highlights
Ignored Files
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request migrates the metadata and telemetry configuration storage from Google Cloud Firestore to a local file-based caching system combined with direct fetching from the GitHub API. Key changes include the introduction of concurrent fetching logic for standard modules and blueprints, the removal of the Firestore dependency from the Go modules, and the implementation of local JSON storage for user telemetry preferences. Feedback focuses on resolving a missing import for YAML parsing, improving the robustness of GitHub API requests by adding a User-Agent header and context timeouts, and ensuring that errors during local cache writes are properly handled rather than ignored.
7107ddd
into
GoogleCloudPlatform:develop
This pull request transitions the telemetry configuration and metadata management from a remote Firestore dependency to a local file-based caching mechanism. This change enhances the robustness of the CLI by removing reliance on external database services for core functionality, ensuring consistent behavior across different environments and improving performance by reducing network overhead.
Changes: