DBAAS-7537: Add do_settings.service_cnames support to Databases API#1137
Merged
SSharma-10 merged 1 commit intodigitalocean:mainfrom Feb 6, 2026
Conversation
This change adds support for custom service CNAMEs (do_settings.service_cnames) to the Managed Databases API for both cluster creation and read replica creation. Changes: - Add new do_settings.yml model with service_cnames array field - Add do_settings field to database_cluster and database_cluster_read models - Add do_settings field to database_replica and database_replica_read models - Update databases_create_cluster.yml with example using service_cnames - Update databases_create_replica.yml with example using service_cnames - Update response examples to include do_settings - Update curl, Go, and Python code examples The service_cnames field allows users to specify custom CNAMEs for their database clusters. Each CNAME must be a valid RFC 1123 hostname (e.g., "db.example.com"), with a maximum of 16 CNAMEs allowed, each up to 253 characters in length.
SSharma-10
reviewed
Feb 6, 2026
| SizeSlug: "db-s-2vcpu-4gb", | ||
| NumNodes: 2, | ||
| StorageSizeMiB : 61440, | ||
| DOSettings: &godo.DOSettings{ |
Contributor
There was a problem hiding this comment.
Do you plan to add this field to the DatabaseCreateRequest struct in godo later? It doesn’t seem to be there currently
Contributor
Author
There was a problem hiding this comment.
Yes, a follow-up PR to digitalocean/godo will be needed to add the DOSettings field to DatabaseCreateRequest and DatabaseCreateReplicaRequest structs. This OpenAPI change needs to merge first, then we can update godo to match.
Contributor
Author
There was a problem hiding this comment.
This was referenced Feb 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change adds support for custom service CNAMEs (do_settings.service_cnames) to the Managed Databases API for both cluster creation and read replica creation.
Changes:
The service_cnames field allows users to specify custom CNAMEs for their database clusters. Each CNAME must be a valid RFC 1123 hostname (e.g., "db.example.com"), with a maximum of 16 CNAMEs allowed, each up to 253 characters in length.