Skip to content

Cut over to machines API for certs, add ownership record + imports#4739

Merged
bglw merged 2 commits intomasterfrom
liam/machines-api-certs
Feb 12, 2026
Merged

Cut over to machines API for certs, add ownership record + imports#4739
bglw merged 2 commits intomasterfrom
liam/machines-api-certs

Conversation

@bglw
Copy link
Contributor

@bglw bglw commented Feb 12, 2026

Change Summary

Certificates are now (primarily) serviced through the Machines API rather than GraphQL.

Alongside this change, support for custom certificate uploads has been introduced, as well as a new DNS entry that can verify ownership of a domain in certain circumstances.

@bglw bglw merged commit 91387ba into master Feb 12, 2026
24 checks passed
@bglw bglw deleted the liam/machines-api-certs branch February 12, 2026 11:43
@amo13
Copy link
Contributor

amo13 commented Feb 13, 2026

Awesome! Are the machines API endpoints for this documented yet? I was not able to find info about them.

@bglw
Copy link
Contributor Author

bglw commented Feb 13, 2026

Soon @amo13 ! These ones need some coercing into the spec that generates the documentation website. In the meantime you can infer them pretty well from the fly-go changes here: https://github.com/superfly/fly-go/pull/208/changes

I'll get the documentation shored up in the new week :)

@bglw
Copy link
Contributor Author

bglw commented Feb 18, 2026

@amo13 docs are up at https://fly.io/docs/machines/api/certificates-resource/ and https://docs.machines.dev/

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