DIGITALOCEAN: DOCS: Refresh digital ocean provider docs

[chicks-net]

Done

• [docs] Refresh digital ocean provider docs by clarifying which record types are supported, linking to the digital ocean docs, and calling out other relevant internal docs.
• spelling correction
• update docs for chicks-net as maintainer for digital ocean

Meta

(Automated in .just/gh-process.just.)

[chicks-net]

Thank you for catching this. I've tried a variety of relative incantations and none seem to work so far. I feel like ../commands/creds-json#example-commands should work - see https://docs.dnscontrol.org/~/revisions/0Am6Ovu9k4Q2mNtPFZC6/provider/digitalocean and b142af2 for it not working.

I might try a few more combinations, but I'm out of ideas.

[chicks-net]

I finally found the right combination when I found an example. I was having trouble finding an example because noone else is referring directly to the commands directory.

Is there any more that should be done for this PR?

[cafferata]

No, that was all.

[cafferata]

These rejects could/should be added to

dnscontrol/providers/digitalocean/auditrecords.go

Line 13 in 9353554

func AuditRecords(records []*models.RecordConfig) []error {

[chicks-net]

Absolutely agree that some of this research needs to get carried over into code. I'm planning on circling back with that soon. I'm still trying to figure out what the code-level priorities should be to have this provider following the project's best practices. 😁

[chicks-net]

@tlimoncelli @cafferata am I supposed to merge this? I don't seem to have that ability.

[tlimoncelli]

@tlimoncelli @cafferata am I supposed to merge this? I don't seem to have that ability.

I do the merging. :)

I assume something is ready to merge once it is no longer in "draft" mode and has the appropriate approvals. (We should probably document that.)