MKTRUE-IMPORT(1)mktrue 1.3.1MKTRUE-IMPORT(1)

mktrue import

NAME

mktrue import — lift a template’s files out of a product

SYNOPSIS

mktrue import --from <dir> --template <name> [--write | --adopt-template]

DESCRIPTION

import is how the templates are refreshed from products that use them. It reads a product under the method and lifts out the files its template’s manifest names.

It is a dry run unless --write. --from names the product to read, and --template the template to import into. --adopt-template records the template’s baseline and writes no file but template.json.

It runs from the kit repository, the one that holds the templates. Most people never need it.

OPTIONS

--from <dir>
The product to import from, under the method.
--template <name>
The template to import into.
--write
Apply the plan: write the lifted files and record them in template.json. Nothing is committed.
--adopt-template
Record the template’s present files as the baseline. Writes no file but template.json.
--help
Print this screen: the command’s usage, its flags and its exit codes.

EXIT STATUS

0true: everything asked for passed.
1findings: a refusal, such as a secret or a file the template does not have, or a write that failed before anything moved.
2usage: not run from the kit repository, or a template it does not have.
4a decision is needed: a file has no baseline, or changed on both sides.

EXAMPLES

import runs from the kit repository. Anywhere else, this is what it says.

exit 2
mktrue import --from . --template applicationmktrue: ✗ import · there is no template called application  why   the manifest names the files to lift, and it is not there  fix   run import from the kit repository, and name a template it has  exit  2

Real output from mktrue 1.3.1, captured with NO_COLOR set.

SEE ALSO