Gcp region is set hard to "us-central1"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 383
- Forks
- 93
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 1
Description
I tried so set my compute region to "west europe" using the gcp console.
Did not work, jobs where always started in "us-central1".
Turns out, the region is hardcoded in tensorflow-cloud.
The implementation in /core/gcp.py is:
def get_region():
return "us-central1"
Please change it to use the default region from gcp, or let us pass in the region as parameter.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in core/gcp.py at get_region(), which currently returns "us-central1". Review how the repository obtains or passes the GCP region, then verify the implementation can honor the user's configured region or an explicit parameter. Done means jobs no longer always default to "us-central1" when another region is selected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, python
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100