Build DNS Automation at Onboarding — Manual Console Before a 2-Path Provisioning Pipeline

Описание и применение

Автоматизация DNS‑изменений при подключении клиентов разделена на два пути: полностью автоматизированный процесс для зон, принадлежащих платформе, и инструктивный процесс для клиентских зон. Внедряется состояние‑машина, которая отслеживает прогресс и обеспечивает идемпотентность повторных попыток.

Задача

Onboarding custom domains requires DNS changes that are currently handled manually, creating an untracked work queue and inconsistent visibility for on‑call engineers.

Результат

The two‑path pipeline reduces manual toil, provides clear state visibility, and ensures idempotent retries. Platform‑owned zones are fully automated; customer‑owned zones receive precise instructions and observation. Inventory tooling improves on‑call diagnostics.

Рабочий процесс

• 1. Store custom domain request with stable ID and ownership mode.
• 2. If platform‑owned, derive desired record set and apply via provider API.
• 3. If customer‑owned, generate exact record instructions and send to customer.
• 4. Observe zone for expected records; retry if not observed.
• 5. Transition state machine accordingly; log each transition.
• 6. On failure, provide rollback guidance (platform: revert to previous state; customer: resend instructions).

Доказательства

Keep DNS changes in a documented manual console process while they are a handful of static records for one company site; build automation when custom-domain setup becomes a repeated part of customer onboarding

Источник

Two ownership paths need different failure states

Источник