Replace the Datastore and Firestore locational endpoints URL examples

[aristide-n]

Description

Replace the Datastore and Firestore locational endpoints URL examples with regional endpoints URLs

Checklist

• I have followed Sample Guidelines from AUTHORING_GUIDE.MD
• README is updated to include all relevant information
• Tests pass: nox -s py-3.9 (see Test Environment Setup)
• Lint pass: nox -s lint (see Test Environment Setup)
• These samples need a new API enabled in testing projects to pass (let us know which ones)
• These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
• This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample
• This sample adds a new Product API, and I updated the Blunderbuss issue/PR auto-assigner with the codeowners for this sample
• Please merge this PR for me once it is approved

[gemini-code-assist]

Summary of Changes

Hello @aristide-n, 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 updates the example code for Google Cloud Datastore and Firestore to reflect current best practices for connecting to these services. Specifically, it replaces outdated locational endpoint URLs with the appropriate regional endpoint URLs in the provided Python snippets, ensuring the samples are accurate and functional.

Highlights

• Datastore Endpoint Update: The Datastore regional endpoint example in datastore/cloud-client/snippets.py has been updated to use the new regional URL https://datastore.africa-south1.rep.googleapis.com instead of the older https://nam5-datastore.googleapis.com.
• Firestore Endpoint Update: The Firestore regional endpoint example in firestore/cloud-client/snippets.py has been updated to use the new regional URL firestore.africa-south1.rep.googleapis.com instead of the older nam5-firestore.googleapis.com.

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 updates the example endpoint URLs for Datastore and Firestore to use regional endpoints instead of multi-regional ones. The changes are correct, but I've suggested a minor improvement in the Firestore snippet to add the https:// scheme to the endpoint URL for consistency and to follow API documentation.

[gemini-code-assist]

For consistency with the Datastore snippet in this same pull request, and to align with the google-api-core ClientOptions documentation (which states api_endpoint should be the full URL including the scheme), it's better to include the https:// prefix here.

Suggested change

	ENDPOINT = "firestore.africa-south1.rep.googleapis.com"
	ENDPOINT = "https://firestore.africa-south1.rep.googleapis.com"

[glasnt]

Is there a reason why these are changing from North America multi-regional to Johannesburg regional? Is it because we don't want to use us-central1 as default?