Skip to content

Add optional subnet_uuid to Droplet create requests - #2

Merged
ddatta-do merged 1 commit into
add-subnet-uuidfrom
copilot/add-subnet-uuid-field-again
Sep 17, 2026
Merged

ddatta-do merged 1 commit into
add-subnet-uuidfrom
copilot/add-subnet-uuid-field-again

Conversation

Copilot AI commented Sep 17, 2026

Copy link
Copy Markdown

Droplet requests accept a vpc_uuid but had no way to pin a Droplet to a specific VPC subnet. subnet_uuid already exists on the Droplet response model; this adds the matching optional request field.

Changes

  • droplets/models/droplet_create.yml: adds optional subnet_uuid (string) next to vpc_uuid. Shared by single and multi create, so both request bodies pick it up. Not added to required; omitting it keeps the current default-subnet behavior.
  • Examples: subnet_uuid added to the create request examples — shared examples.yml (single + multi), curl, python, ruby.
vpc_uuid: 760e09ef-dc84-11e8-981e-3cfdfeaae000
subnet_uuid: 9c7a0d63-3c4e-4d3d-9f56-3b0fb0e5e4a1

Wording of the field description ("assigned to a default subnet of the VPC" when excluded) is worth a check against the intended API semantics.

Co-authored-by: ddatta-do <147642663+ddatta-do@users.noreply.github.com>
@ddatta-do
ddatta-do marked this pull request as ready for review September 17, 2026 14:25
@ddatta-do
ddatta-do merged commit 25111f4 into add-subnet-uuid Sep 17, 2026
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