dna solution

Scaffold and update a repo from Copier templates.

dna solution new renders one app; running it again with a different service name overlays a SECOND app from the same template, with its own answers file. dna solution update rolls one of them forward.

Rendering always happens here, on this machine, from a template you point at — never on a server, and never with --trust.

Generated from the command definitions

This page is introspected from the dna Click command tree by scripts/gen_cli_docs.py, so it stays in lockstep with dna solution --help.

dna solution list

List the template layers recorded in DESTINATION.

One row per answers file — which is one row per app, because the design is one template overlaid N times, each with its own answers and its own independent update.

dna solution list [OPTIONS] [DESTINATION]

Arguments

Argument	Required
DESTINATION	no

Options

Option	Description
--help	Show this message and exit.
--json	Machine-readable listing.

dna solution new

Render TEMPLATE into DESTINATION, recording the answers.

TEMPLATE is anything Copier accepts: a local path, a git URL, gh:owner/repo. Run it once per app; each run writes its own answers file, and each app is then updated independently.

dna solution new [OPTIONS] TEMPLATE DESTINATION

Arguments

Argument	Required
TEMPLATE	yes
DESTINATION	yes

Options

Option	Description
--answers-from	YAML file of answers, applied under --data. The hand-rolled precursor of a recorded Solution.
--defaults	Take the template's default for every question that was not answered.
--force	Overwrite files that already exist.
--help	Show this message and exit.
--json	Machine-readable report.
--pretend	Render nothing; report what would happen.
--scope	The DNA scope holding the Solution instance.
--solution	Record this run in the Solution instance NAME — the declaration and the answers as governed data. It is what lets a when:-gated answer survive the update that erases it from the answers file.
--strict	Exit 3 when the run has findings (missing inherited data, a recorded service whose App never answered the cost question).
--vcs-ref	Template ref to render (tag, branch or commit). Default: the latest tag.
-d, --data	Answer a question without being asked. Repeatable.

dna solution record

Record DESTINATION's template layers in a Solution instance.

The declaration and the answers become governed data — versioned, overlayable, and readable across the fleet without opening anybody's repo.

Records EVERY layer by default: this is what an existing tree needs, and a record that covered some of a repo's apps would answer "which of them may sleep?" with a number that is wrong and looks right. -a/-s narrow it to one on purpose.

It stores no code and no template body — a template.src + ref pointer and the answers verbatim. The cost commitment is NOT stored here: it is read off the App of the same name (can_sleep), and services whose App has not answered are reported on every run.

dna solution record [OPTIONS] [DESTINATION]

Arguments

Argument	Required
DESTINATION	no

Options

Option	Description
--app	An App this solution delivers. Repeatable. REPLACES the recorded list when given — and must then name EVERY recorded service: apps is the only join the kernel can enforce, and an App IS a deployment. A list that leaves one out is refused with both sides named. Rarely needed; the recorded layers already fill it.
--description	One line of what it delivers.
--help	Show this message and exit.
--json	Machine-readable report.
--scope	The DNA scope holding the instance.
--solution	The Solution instance to write.
--strict	Exit 3 when a recorded service has no App answering the cost question.
--title	Human title (default: the name).
-a, --answers-file	Record only this answers file.
-s, --service	Record only this service.

dna solution update

Roll ONE app in DESTINATION forward to a newer template version.

The recorded answers are always re-passed, so nothing is re-asked and nothing is silently re-defaulted. Whatever the update leaves behind or drops is named in the report — that reporting is the reason this command exists rather than a copier update alias.

With --solution NAME the recorded instance joins the answers file as a second, LONGER memory: the two are merged before anything is compared or re-passed, so an answer when: erased from the file comes back as the human's value instead of the template's default, and the merged set is written back afterwards.

dna solution update [OPTIONS] [DESTINATION]

Arguments

Argument	Required
DESTINATION	no

Options

Option	Description
--adopt-new-defaults	Take every default that moved since the recorded ref (see the report).
--allow-untagged	Proceed even though the template publishes no tags.
--answers-from	YAML file of answers to apply over the recorded ones.
--conflict	How Copier records a conflict. (default: inline)
--help	Show this message and exit.
--json	Machine-readable report.
--pretend	Change nothing; report what would happen.
--scope	The DNA scope holding the Solution instance.
--solution	Record this run in the Solution instance NAME — the declaration and the answers as governed data. It is what lets a when:-gated answer survive the update that erases it from the answers file.
--strict	Exit 3 when the run has findings (lost answers, conflicts, defaults left behind, a recorded service whose App never answered the cost question).
--vcs-ref	Update to this ref instead of the latest tag.
-a, --answers-file	The answers file to update, relative to DESTINATION.
-d, --data	Move an answer as part of this update. Repeatable.
-s, --service	Shorthand for -a .copier-answers..yml.