Skip to content

Use locations instead of supported_regions#439

Open
aswink wants to merge 1 commit intomainfrom
aswin/04-10-use_locations_instead_of_supported_regions
Open

Use locations instead of supported_regions#439
aswink wants to merge 1 commit intomainfrom
aswin/04-10-use_locations_instead_of_supported_regions

Conversation

@aswink
Copy link
Copy Markdown
Contributor

@aswink aswink commented Apr 10, 2026

I just noticed that we already had a locations field, so revert the
supported_regions change I made in favor of locations, and actually update
those vertex models to have the correct locations. Also update them to add
available_providers to ["vertex"].

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 10, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
ai-proxy Ready Ready Preview, Comment Apr 11, 2026 5:03am

Request Review

Copy link
Copy Markdown
Contributor Author

aswink commented Apr 10, 2026

This stack of pull requests is managed by Graphite. Learn more about stacking.

@aswink aswink marked this pull request as ready for review April 10, 2026 20:51
@aswink aswink force-pushed the aswin/04-10-use_locations_instead_of_supported_regions branch from 4441e65 to 3ee820b Compare April 10, 2026 20:53
Comment on lines -2927 to -2929
"supported_regions": [
"global"
],
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

should we specify locations for specific models?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

after your comment on the other PR I realized that this wasn't vertex, this is google, which is why this was removed here

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4441e656c6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "Codex (@codex) review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".

@aswink aswink force-pushed the aswin/04-10-use_locations_instead_of_supported_regions branch from 3ee820b to ae11cf3 Compare April 10, 2026 21:04
@aswink aswink force-pushed the aswin/04-10-use_locations_instead_of_supported_regions branch from ae11cf3 to a5473d3 Compare April 10, 2026 21:08
@aswink aswink force-pushed the aswin/04-10-use_locations_instead_of_supported_regions branch from a5473d3 to 5458805 Compare April 10, 2026 22:27
I just noticed that we already had a locations field, so revert the
supported_regions change I made in favor of locations, and actually update
those vertex models to have the correct locations. Also update them to add
available_providers to ["vertex"].
@aswink aswink force-pushed the aswin/04-10-use_locations_instead_of_supported_regions branch from 5458805 to 1e17594 Compare April 11, 2026 05:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants