Domain names become an allocatable resource with one authority. A new core module (schema `domains`, own migration stream between core and the integrations) owns claims — a DNS node plus its whole subtree, mutually disjoint: operator shared-domain roots, member claims carved from them, and bring-your-own names proven by TXT verification — and placements, which bind a name inside a claim to a provider slug and resource ref. Verification moves to the claim and decouples from creation. A member proves control of a domain once; afterwards every name inside it places instantly, wildcard-CNAME friendly, with no further DNS work. The claim workflow activates the claim and stops — it no longer creates a site — so the sites list offers a one-click create once a domain verifies. /domains/ask answers from placements and is registered by core rather than the FedWiki adapter; its HTTP contract is unchanged. A configured `domains-ask-fallback-url` forwards names the registry does not know to a legacy answerer, the strangler seam wiki.cafe's migration needs; a name the registry knows but has archived is refused locally. FedWiki's create saga reserves the name before the farm call, carrying a workflow-minted site id so retries are idempotent, and compensates on failure. Sync places only names it owns, never stealing a member's; lifecycle transitions and the retention purge maintain servability. An unconditional boot pass seeds operator roots, releases orphaned placements, and adopts pre-existing sites — grandfathering member-owned external domains shortest-name-first, and skipping name policy, so a live single-letter site cannot lose its certificate. Members manage domains at /domains: claims with verification status, DNS records including an optional wildcard row, check-now, cancel, release. Name policy (reserved, blocked, premium, plus a single-letter guard) is operator data; refusals collapse to a plain "unavailable" so the console never becomes an oracle for who holds what. BREAKING (pre-release): `fedwiki.custom_domain_verifications` and `sites.is_custom_domain` are dropped, the flag now derived from the placement's claim kind; resource key `fedwiki_custom_domains` migrates to the platform-owned `external_domain_claims`; running verify-custom-domain workflows must be terminated before deploy.
37 lines
1.2 KiB
YAML
37 lines
1.2 KiB
YAML
version: "2"
|
|
sql:
|
|
- engine: "postgresql"
|
|
schema:
|
|
- "../db/migrations/"
|
|
- "migrations/"
|
|
- "../db/sqlc_schemas.sql"
|
|
queries: "queries/"
|
|
gen:
|
|
go:
|
|
package: "domains"
|
|
out: "."
|
|
sql_package: "database/sql"
|
|
emit_json_tags: true
|
|
emit_prepared_queries: false
|
|
emit_interface: true
|
|
emit_exact_table_names: false
|
|
emit_empty_slices: true
|
|
omit_unused_structs: true
|
|
rename:
|
|
# Registry models. Pinned so the `domains` schema prefix sqlc
|
|
# would otherwise fold into the struct name stays out of this
|
|
# package's own API (it is already the package name).
|
|
domains_claim: Claim
|
|
domains_claims: Claim
|
|
domains_placement: Placement
|
|
domains_placements: Placement
|
|
domains_name_rule: NameRule
|
|
domains_name_rules: NameRule
|
|
# Core spillover tables are pulled in by ../db/migrations/ but no
|
|
# query here touches them, so omit_unused_structs drops them. A
|
|
# query that starts joining core must add the canonical rename
|
|
# entries -- see internal/integration/sqlc.yaml for the mapping.
|
|
overrides:
|
|
- db_type: "uuid"
|
|
go_type: "string"
|