Skip to content

DIGITALOCEAN: Update feature table for provider#3958

Merged
tlimoncelli merged 2 commits intoStackExchange:mainfrom
chicks-net:chicks/2026-01-05-digitalocean-feature-flags
Jan 6, 2026
Merged

DIGITALOCEAN: Update feature table for provider#3958
tlimoncelli merged 2 commits intoStackExchange:mainfrom
chicks-net:chicks/2026-01-05-digitalocean-feature-flags

Conversation

@chicks-net
Copy link
Copy Markdown
Collaborator

@chicks-net chicks-net commented Jan 5, 2026

Summary

This PR clarifies the DigitalOcean provider's capabilities by replacing question marks () with explicit feature flags in both the provider code and documentation tables.

Changes

  • Updated providers/digitalocean/digitaloceanProvider.go to explicitly declare support or lack of support for 15 additional record types and features
  • Updated documentation/provider/index.md to reflect these explicit capabilities in the provider feature tables
  • All changes based on DigitalOcean's API documentation

Features Now Explicitly Documented

Supported:

  • SOA records (Can)
  • CAA records (already documented, maintained)
  • SRV records (already documented, maintained)
  • Concurrency (Can)
  • Get Zones (Can)

Not Supported (per DigitalOcean docs):

  • ALIAS, DNAME records
  • DNSSEC-related: DNSKEY, DS, AutoDNSSEC
  • DHCID, HTTPS, LOC, NAPTR, PTR, SMIMEA, SSHFP, SVCB, TLSA records

Testing was done

These are documentation/capability declaration changes only - no functional code changes. Unit tests ran locally without errors and the docs generated without errors.

The capabilities system will now properly validate configurations against DigitalOcean's actual limitations.

Something to consider

The commands/types/dnscontrol.d.ts file changes during documentation generation, but I haven't added that to this PR because it seems unrelated. Claude also thinks that this file is why the check-git-status GHA is failing. Should I go ahead and add this file to prevent this from tripping up future PRs?

🤖 PR summary initially generated with Claude Code

Co-Authored-By: Claude Sonnet 4.5 [email protected]

@chicks-net chicks-net requested a review from tlimoncelli January 5, 2026 15:52
@tlimoncelli
Copy link
Copy Markdown
Contributor

Yes, please run bin/generate-all.sh to regenerate that file (and others).

@chicks-net
Copy link
Copy Markdown
Collaborator Author

Yes, please run bin/generate-all.sh to regenerate that file (and others).

I had already done that. After that, I wasn't clear whether git add .; git push was the desired action for files that seem to be unrelated changes. 52b8d40 adds the unrelated file to this PR and all of the GHA checks are happy now.

@tlimoncelli tlimoncelli changed the title DIGITALOCEAN: explicit feature flags remove ?s in feature table DIGITALOCEAN: Update feature table for provider Jan 6, 2026
@tlimoncelli tlimoncelli merged commit 704cb7f into StackExchange:main Jan 6, 2026
6 checks passed
tlimoncelli pushed a commit that referenced this pull request Jan 29, 2026
)

#3958 updated the digitalocean provider to make all of the feature flags
explicit.

Later I noticed that `Cannot()` can take an argument so that the reason
for it can
be seen by the end user. So now I have moved the reason into the
argument instead
of leaving it as a code-level comment.

- `dnscontrol` rebuilt fine
- `bin/generate-all.sh` picked up an unrelated file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants