Skip to content

microvms: add egress policy to MicroVM and create request (MDROP-608) - #1188

Merged
SSharma-10 merged 1 commit into
digitalocean:mainfrom
sgupta832:MDROP-608/godo-egress-policy
Oct 23, 2026
Merged

SSharma-10 merged 1 commit into
digitalocean:mainfrom
sgupta832:MDROP-608/godo-egress-policy

Conversation

@sgupta832

Copy link
Copy Markdown
Contributor

Adds the per-MicroVM egress policy to the MicroVM API types so clients (doctl, terraform) can set it at create and read it back.

Changes

  • New MicroVMEgressPolicy (default_action + rules), MicroVMEgressRule (exactly one of domain or ip) and MicroVMEgressAction (deny / allow).
  • EgressPolicy *MicroVMEgressPolicy on MicroVMCreateRequest and MicroVM. A nil policy means unrestricted egress (or, on a checkpoint restore, inheriting the origin's policy).
  • Test covering the create request body and the decoded response.

The policy is only valid with public networking, is fixed at create, and rules match the host only (no CIDR, no ports); the API enforces this.

Follow-ups: doctl (MDROP-608) and the Terraform provider (MDROP-609) will consume this once it is released.

Made with Cursor

@SSharma-10
SSharma-10 merged commit 1f87107 into digitalocean:main Oct 23, 2026
8 checks passed
@sgupta832 sgupta832 mentioned this pull request Oct 23, 2026
@SSharma-10 SSharma-10 mentioned this pull request Oct 26, 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

⌂ 换网址