fix!: making location field as required for standard cluster

[Daisyprakash]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @Daisyprakash, I'm Gemini Code Assist¹! 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 robustness of standard GKE cluster deployments by making the 'location' parameter a mandatory input. This change ensures that all new cluster creations explicitly define their geographical deployment region or zone, preventing misconfigurations and aligning with best practices for resource provisioning.

Highlights

• Mandatory Location Field: The 'location' parameter for standard GKE clusters is now explicitly required, ensuring that a region or zone is always specified during cluster creation.
• Configuration Updates: The module's configuration files (metadata.yaml, variables.tf) have been updated to enforce the 'location' field as mandatory.
• Documentation Alignment: The README.md has been updated to reflect that the 'location' parameter is now required and no longer has a default value.

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. ↩

[gemini-code-assist]

Code Review

This pull request correctly makes the location field for the standard GKE cluster a required input. The changes are consistently applied across the Terraform variable definition, the module metadata, and the documentation. I have one point of feedback regarding the UI display metadata for the location field, which appears to have an inconsistent change that might affect user experience.

[apeabody]

/gcbrun

[apeabody]

Thanks for the contribution @Daisyprakash

[apeabody]

/gcbrun

[apeabody]

/gcbrun