Generated Files Without the Silent Overwrite: Why TDK CLI Treats Local Config as Derived Artifacts

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

TDK CLI генерирует все необходимые файлы конфигурации из одного декларативного service.json, защищая ручные изменения с помощью детекции дрейфа и предлагая явный регенерацию или игнорирование.

Задача

Maintaining consistent local infrastructure files (Dockerfiles, Vite configs, nginx configs, etc.) across many services is error‑prone and tedious, especially when AI writes application code but not the surrounding configs.

Результат

TDK CLI automates generation of all local infrastructure files, treats them as derived artifacts, and provides explicit drift handling to protect hand‑edited customizations, ensuring consistency across services without silent overwrites.

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

• Write a service.json for each service
• Run tdk up to generate config files and start Tilt/Docker environment
• If a generated file is edited, tdk up detects drift and exits with code 2
• Choose to regenerate with tdk config regenerate or run tdk up --ignore-drift to keep customizations

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

TDK generates the rest (roughly 17 files for a typical frontend) and treats those outputs as derived artifacts rather than source.

Источник

If you edit a generated file by hand, tdk up detects the drift (against a stored snapshot) and stops with exit code 2 instead of silently overwriting.

Источник