From 265ba457742bd6dde91f9acfa8ae254c031674c3 Mon Sep 17 00:00:00 2001 From: Kate Erickson Date: Mon, 27 Jul 2026 14:36:26 -0600 Subject: [PATCH 1/2] Complete databases firewall PUT description (PDOCS-4399) Fix truncated success sentence and document IPv6 unsupported plus limits page link. --- .../databases/databases_update_firewall_rules.yml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/specification/resources/databases/databases_update_firewall_rules.yml b/specification/resources/databases/databases_update_firewall_rules.yml index ea49be267..553aad12c 100644 --- a/specification/resources/databases/databases_update_firewall_rules.yml +++ b/specification/resources/databases/databases_update_firewall_rules.yml @@ -9,12 +9,15 @@ description: >- able to open connections to the database. You may limit connections to specific Droplets, Kubernetes clusters, or IP addresses. When a tag is provided, any Droplet or Kubernetes node with that tag applied to it will - have access. The firewall is limited to 100 rules (or trusted sources). When - possible, we recommend + have access. The firewall is limited to 100 rules (or trusted sources). You + cannot add IPv6 addresses as trusted sources. For additional limits, see your + database engine's limits page, for example + [PostgreSQL Limits](https://docs.digitalocean.com/products/databases/postgresql/details/limits/). + When possible, we recommend [placing your databases into a VPC network](https://docs.digitalocean.com/products/networking/vpc/) to limit access to them instead of using a firewall. - A successful + A successful request returns a 204 status code with no content. tags: - Databases From b681acb8cbda100c6f94a300f828daf010d1bc64 Mon Sep 17 00:00:00 2001 From: Kate Erickson Date: Mon, 27 Jul 2026 14:43:48 -0600 Subject: [PATCH 2/2] Drop PostgreSQL limits example link from firewall description --- .../resources/databases/databases_update_firewall_rules.yml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/specification/resources/databases/databases_update_firewall_rules.yml b/specification/resources/databases/databases_update_firewall_rules.yml index 553aad12c..78d6361b4 100644 --- a/specification/resources/databases/databases_update_firewall_rules.yml +++ b/specification/resources/databases/databases_update_firewall_rules.yml @@ -11,8 +11,7 @@ description: >- provided, any Droplet or Kubernetes node with that tag applied to it will have access. The firewall is limited to 100 rules (or trusted sources). You cannot add IPv6 addresses as trusted sources. For additional limits, see your - database engine's limits page, for example - [PostgreSQL Limits](https://docs.digitalocean.com/products/databases/postgresql/details/limits/). + database engine's limits page. When possible, we recommend [placing your databases into a VPC network](https://docs.digitalocean.com/products/networking/vpc/) to limit access to them instead of using a firewall.