Skip to content

Graduate network/private-service-access to core modules#5029

Merged
SwarnaBharathiMantena merged 2 commits intoGoogleCloudPlatform:developfrom
SwarnaBharathiMantena:swarnabm/move-comm-mod-network-psa
Dec 26, 2025
Merged

Graduate network/private-service-access to core modules#5029
SwarnaBharathiMantena merged 2 commits intoGoogleCloudPlatform:developfrom
SwarnaBharathiMantena:swarnabm/move-comm-mod-network-psa

Conversation

@SwarnaBharathiMantena
Copy link
Contributor

The private-service-access module configures private service access for the VPC specified by the network_id variable. It can be used by the Cloud SQL Federation module or to connect Google Cloud NetApp Volumes.

The private-service-access module needs to be moved from the community/modules/network folder to the modules/network folder.

Note: "community/modules/network/private-service-access": "modules/network/private-service-access" has been added to movedModules map in the pkg/config/config.go file. This ensures that any blueprint deployment using the path "community/modules/network/private-service-access" errors out with a message: Error: a module has moved. community/modules/network/private-service-access has been replaced with modules/network/private-service-access. Please update the source in your blueprint and try again.

@SwarnaBharathiMantena SwarnaBharathiMantena added the release-breaking-changes Prevents "smooth" re-deploy across versions label Dec 22, 2025
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @SwarnaBharathiMantena, 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 focuses on graduating the 'private-service-access' module by moving it from the 'community' section to the core 'modules' directory. This change reflects the module's stability and importance, making it a standard offering. The update includes adjusting all internal references across various examples and documentation files to point to the new path, along with implementing a robust redirection mechanism for users still referencing the old path, ensuring a smooth transition and clear guidance.

Highlights

  • Module Relocation: The 'private-service-access' module has been moved from the 'community/modules/network' directory to the 'modules/network' directory, signifying its graduation to a core module.
  • Reference Updates: All blueprint examples, documentation, and configuration files that previously referenced the module have been updated to reflect its new, canonical location.
  • Backward Compatibility: An entry has been added to the 'movedModules' map in 'pkg/config/config.go' to ensure that deployments using the old module path will receive an informative error message, guiding them to update their blueprints.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request primarily re-paths the private-service-access module from community/modules/network/private-service-access to modules/network/private-service-access. This change is reflected across numerous example YAML configuration files, module READMEs, Terraform files (main.tf, variables.tf), and internal configuration files (pkg/config/config.go), indicating a formal relocation of the module within the project structure. There were no review comments provided.

@SwarnaBharathiMantena
Copy link
Contributor Author

SwarnaBharathiMantena commented Dec 26, 2025

community/examples

  • slurm-gke - PR-test-slurm-gke - success - link
  • hpc-slurm-gromacs - PR-test-spack-gromacs - success - link
  • hpc-slurm-local-ssd - PR-test-slurm-gcp-v6-ssd - success - link
  • hpc-slurm-ubuntu2204 - PR-test-slurm-gcp-v6-ubuntu - success - link
  • htc-slurm - PR-test-htc-slurm - success - link

Examples

  • gke-a3-ultragpu - PR-test-gke-a3-ultragpu-onspot - success - link
  • gke-a4 - PR-test-gke-a4 - success - link
  • gke-a4x - PR-test-gke-a4x - success - link
  • gke-tpu-7x-advanced - no PR test for the advanced yaml
  • gke-tpu-v6-advanced - no PR test for the advanced yaml
  • gke-managed-lustre - PR-test-gke-managed-lustre - success - link
  • hcls-blueprint - PR-test-hcls - success - link
  • hpc-enterprise-slurm - PR-test-hpc-enterprise-slurm - success - link
  • hpc-slurm - PR-test-slurm-gcp-v6-rocky8 - success - link
  • ml-slurm - PR-test-ml-slurm - success - link
  • netapp-volumes - PR-test-netapp-volumes - success - link
  • pfs-managed-lustre-slurm - PR-test-pfs-managed-lustre-slurm - success - link
  • pfs-managed-lustre-vm - PR-test-pfs-managed-lustre-vm - success - link

example/machine-learning

  • a3-megagpu-8g - PR-test-ml-a3-megagpu-onspot-slurm-ubuntu - success - link
  • a3-ultragpu-8g - PR-test-ml-a3-ultragpu-onspot-slurm - success - link
  • a4-highgpu-8g - PR-test-ml-a4-highgpu-slurm - success - link
  • a4x-highgpu-4g - no PR test

PR-validation test - success - link

@SwarnaBharathiMantena SwarnaBharathiMantena merged commit e07791c into GoogleCloudPlatform:develop Dec 26, 2025
29 of 70 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-breaking-changes Prevents "smooth" re-deploy across versions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants