[Telemetry] Add support to collect the Deployment File name#5539
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 enhances the telemetry collection capabilities of the cluster toolkit by tracking the deployment file used during operations. It introduces a mechanism to validate and record the deployment file name against a list of predefined examples fetched from the official repository, ensuring that only recognized deployment files are reported. Highlights
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 refactors the GitHub API tree retrieval into a shared helper and introduces telemetry to track the usage of standard deployment files. A logic error was identified in the file path extraction for predefined examples, which would prevent accurate telemetry matching. Additionally, the telemetry collection logic contains dead code and references an undefined variable that need to be addressed.
|
/gemini summary |
Summary of ChangesThis pull request enhances the telemetry collection capabilities of the cluster toolkit by tracking the deployment file used during operations. It introduces a mechanism to validate and record the deployment file name against a list of predefined examples fetched from the official repository, ensuring that only recognized deployment files are reported. Highlights
Activity
|
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request introduces the ability to track standard deployment files in telemetry by fetching them from the GitHub repository. It refactors the module-fetching logic into a shared fetchGitFiles helper and adds a new DEPLOYMENT_FILE metric to the telemetry collector. The review feedback highlights critical performance concerns regarding synchronous network calls during package initialization, which could cause hangs in offline environments. Additionally, suggestions were made to implement caching for API responses and to normalize file paths for more reliable validation.
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request introduces caching for GitHub API responses when fetching predefined modules and examples, improving performance and reducing redundant network calls. It also adds telemetry to track whether a standard or custom deployment file is being used. A review comment suggests improving the error handling in getDeploymentFile to return "UNVERIFIED" and log a warning if the standard file list cannot be fetched, ensuring consistency with the getModules function.
|
/gemini summary |
Summary of ChangesThis pull request enhances the telemetry collection capabilities of the cluster toolkit by tracking the deployment file used during operations. It introduces a mechanism to validate and record the deployment file name against a list of predefined examples fetched from the official repository, ensuring that only recognized deployment files are reported. Highlights
Activity
|
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request introduces telemetry for tracking the deployment file used in Cluster Toolkit commands, including path normalization and classification of standard versus custom files. It also refactors module metadata retrieval into a generic utility. Key feedback points out that the deployment file should be identified via positional arguments to match CLI behavior and recommends moving network-based initialization to a pre-run hook to avoid redundant operations.
|
/gemini review |
|
/gemini summary |
There was a problem hiding this comment.
Code Review
This pull request replaces the Firestore-based metadata caching with a GitHub-API-driven system featuring local file-based caching. It introduces utilities to fetch standard modules, examples, and blueprint names, and enhances telemetry to track deployment files. Review feedback highlights the need for getDeploymentFile to support positional arguments and cross-platform path normalization for Windows. Additionally, it is recommended to remove unused blueprint fetching logic or relocate its initialization to a persistent pre-run hook to optimize performance.
Summary of ChangesThis pull request enhances the telemetry collection capabilities of the cluster toolkit by tracking the deployment file used during operations. It introduces a mechanism to validate and record the deployment file name against a list of predefined examples fetched from the official repository, ensuring that only recognized deployment files are reported. Highlights
Ignored Files
Activity
|
c971d29
into
GoogleCloudPlatform:develop
This pull request enhances the telemetry collection capabilities of the cluster toolkit by collecting the deployment file used during operations. It introduces a mechanism to validate and record the deployment file name against a list of predefined examples fetched from the official repository at the time of the user's version, ensuring that only recognized deployment files are reported.
Changes:
KINDLY NOTE THAT TELEMETRY DATA IS NOT BEING COLLECTED YET.