Skip to content
This repository was archived by the owner on Oct 1, 2026. It is now read-only.

Add region support for ADK agent deployments - #42

Merged
HemasumanthDO merged 1 commit into
digitalocean:mainfrom
HemasumanthDO:hema/add-region-to-adk-deploy
Apr 17, 2026
Merged

HemasumanthDO merged 1 commit into
digitalocean:mainfrom
HemasumanthDO:hema/add-region-to-adk-deploy

Conversation

@HemasumanthDO

@HemasumanthDO HemasumanthDO commented Apr 17, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • Add optional region field to agent config YAML (.gradient/agent.yml)
  • Pass region through to CreateAgentWorkspaceInput and CreateAgentWorkspaceDeploymentInput API calls
  • Add region field to API models, config manager, deploy service, and CLI

Usage

Users can set region in their config:

agent_name: my-agent
agent_environment: main
entrypoint_file: main.py
region: atl1

If omitted, the backend uses its default region.

Test plan

  • Deploy with no region set in config (should use default, no behavior change)
  • Deploy with region: atl1 in config (should pass region to API)
  • Verify gradient agent configure still works without region
  • Verify existing agent configs without region field still work

Made with Cursor

Allow users to specify a deployment region in the agent config YAML.
When set, the region is passed to the API when creating workspaces
and deployments. If omitted, the backend uses its default region.

Config example:
  region: atl1

Made-with: Cursor
@HemasumanthDO
HemasumanthDO merged commit 0cb8461 into digitalocean:main Apr 17, 2026
5 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants