chore: align Batch blueprints with org-wide naming convention#5568
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 updates the naming conventions for Google Cloud Batch components within the Toolkit. By removing 'serverless' and 'cloud' prefixes from blueprints, documentation, and test configurations, the project achieves better consistency with the official product naming. These changes ensure that all references, paths, and test definitions are aligned with the new standard. 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 renames 'serverless-batch' to 'batch' and 'serverless-batch-mpi' to 'batch-mpi' across documentation, example blueprints, and test configurations. Additionally, it updates the default filename for generated batch job templates from cloud-batch-<job_id>.json to <job_id>.yaml in the module's variable descriptions and README. I have no feedback to provide.
There was a problem hiding this comment.
Code Review
This pull request renames the serverless batch examples and blueprints to a more concise "batch" naming convention across documentation, example files, and CI/CD configurations. It also updates the default file extension for generated batch job templates from .json to .yaml in the module documentation and variable definitions. I have no feedback to provide.
…g wide naming convention for this product
1fb9498 to
4c08075
Compare
|
PR test for batch (earlier cloud-batch): https://pantheon.corp.google.com/cloud-build/builds/1df7ff60-c44f-4f1e-97bd-13e08274952b?project=hpc-toolkit-dev PR-test-batch-mpi results: https://pantheon.corp.google.com/cloud-build/builds;region=global/b2edc025-3e3c-43db-a536-a9815411f9f4?project=hpc-toolkit-dev |
79e93d6
into
GoogleCloudPlatform:develop
This PR removes references to "serverless" and "cloud-batch" from Google Cloud Batch blueprints, documentation, and tests. These changes are intended to align the Toolkit with the organization-wide naming convention for the Batch product.
Key Changes
Blueprints & Examples:
Documentation:
Modules:
Tests:
Submission Checklist
NOTE: Community submissions can take up to 2 weeks to be reviewed.
Please take the following actions before submitting this pull request.