deploy & export
deploy and export act on a config artifact type, identified by
its stable type slug.
tcli deploy <type> [flags...]tcli export <type> [flags...]Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
<type> |
The stable type slug sub-command (e.g. preferences), not the friendly display name. Available types come from your project manifest. |
[flags...] |
Flags for any parameters the type’s script declares (see Script params). |
tcli registers a sub-command for every deployable and exportable config artifact. To get a list of the available types, run tcli deploy --help or tcli export --help.
Export parameters
Section titled “Export parameters”If the manifest entry’s exportScript or deployScript declares params, supply
their values as flags after the type’s sub-command:
tcli export workflows --template "TCM Release Process"Use -h or --help to list the available flags:
tcli deploy workflows --helpIn the TUI, a pre-run screen prompts for each parameter before the command runs. Types without parameters run immediately.
Environment
Section titled “Environment”Both commands require TC_ROOT, TC_DATA, and UPG to be resolvable. In
headless mode they must come from .tcli.env.yaml or environment variables.
tcli will not prompt. See Environment resolution.
Exit codes
Section titled “Exit codes”tcli mirrors the underlying process’s exit code.
Example
Section titled “Example”tcli deploy stylesheetstcli export preferences --category General --scope SITEtcli export workflows --template "TCM Release Process"See also
Section titled “See also”- Config artifact types — the full matrix, including what each type’s script expects (where to place files, and which Teamcenter utility runs).