-
Notifications
You must be signed in to change notification settings - Fork 2k
feat: compute_consistency_group_create/delete/(add/remove)disk/list #3918
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
Conversation
|
Here is the summary of changes. You are about to add 5 region tags.
This comment is generated by snippet-bot.
|
3b18981 to
bf8a40f
Compare
69be858 to
36a06cd
Compare
|
@gemini review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This pull request introduces functionalities to manage Compute Engine consistency groups. The implementation looks good overall, and the tests are comprehensive. Here are a few suggestions for improvement:
- Naming Consistency: Consider renaming
callCreateConsistencyGroupindeleteConsistencyGroup.jstocallDeleteConsistencyGroupfor better clarity and consistency with other files. - Error Handling: While the code includes basic error handling in the
mainfunction, consider adding more specific error handling within thecall...functions to provide more informative error messages. - JSDoc Comments: Add JSDoc comments to the functions to explain their purpose, parameters, and return values. This will improve code readability and maintainability.
- Filtering in consistencyGroupDisksList.js: The comment mentions manual filtering is necessary because
disksClient.listdoesn't support filtering yet. It's worth checking the library documentation again to see if filtering is now supported. If so, use the built-in filtering for better performance. - Asynchronous Operations: Ensure all asynchronous operations are handled correctly, especially in the tests. Use
awaitor promises to wait for operations to complete before making assertions. - TODO Comments: Address the TODO comments in the code by providing example values or instructions for the developer.
| * TODO(developer): Update/uncomment these variables before running the sample. | ||
| */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but they already have defined example values- simmilarly to your proposal, the same situation for other samples
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My apologies, I overlooked the existing example values. Given that similar examples are present in other samples, it's likely consistent with the project's style. No further action needed on my part.
| * TODO(developer): Update/uncomment these variables before running the sample. | ||
| */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| * TODO(developer): Update/uncomment these variables before running the sample. | ||
| */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| * TODO(developer): Update/uncomment these variables before running the sample. | ||
| */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| * TODO(developer): Update/uncomment these variables before running the sample. | ||
| */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
b5624de to
49dc25f
Compare
…yGroup.js Co-authored-by: code-review-assist-experimental[bot] <172519755+code-review-assist-experimental[bot]@users.noreply.github.com>
…cyGroup.js Co-authored-by: code-review-assist-experimental[bot] <172519755+code-review-assist-experimental[bot]@users.noreply.github.com>
…yGroup.js Co-authored-by: code-review-assist-experimental[bot] <172519755+code-review-assist-experimental[bot]@users.noreply.github.com>
…yGroup.js Co-authored-by: code-review-assist-experimental[bot] <172519755+code-review-assist-experimental[bot]@users.noreply.github.com>
fea2174 to
a9681c4
Compare
Description
Fixes #
Note: Before submitting a pull request, please open an issue for discussion if you are not associated with Google.
Checklist
npm test(see Testing)npm run lint(see Style)GoogleCloudPlatform/nodejs-docs-samples. Not a fork.