type-bridge-cli 2.2.1

TypeBridge V2 workspace command-line interface
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59

# type-bridge-cli

The `type-bridge` command-line interface for split-YAML workspaces, generated
bindings, and canonical schema migrations. Schema checking, generation, and
migration authoring/planning are offline; apply, verify, and adopt connect only
through an explicitly selected workspace environment.

## Install and start

```bash
cargo install type-bridge-cli --version 2.2.1 --locked
type-bridge --help
type-bridge schema check
type-bridge schema generate
```

Run commands from a workspace containing `typebridge.yaml`, or pass
`--manifest <path>`. Keep credentials as symbolic environment references and
enable migration access explicitly in the chosen environment. The same entry
point is available to Rust integrators as `type_bridge_cli::run_cli`.

Binding-neutral attribute backfills are authored from a closed YAML intent
stored directly in the configured migration directory:

```yaml
format: typebridge.migration-backfill-intent/v1
copy-attribute:
  owner-kind: entity
  owner: person
  source: legacy-name
  destination: display-name
  partition-key: person-id
  batch-rows: 128
  reverse: remove-equal-copied-destination
```

After the schema history reaches the current Split-YAML state, publish the
reviewed intent with:

```bash
type-bridge migration make --name copy-name \
  --backfill-intent copy-name.backfill.yaml
```

The intent filename must be a regular direct child of the migration directory.
The historical owner must have the partition attribute as an effective key,
and the committed head must still equal the current schema sources. The CLI
serializes discovery, parsing, generation, and no-overwrite publication under
one directory lock.

The crate has no optional features. It is released in lockstep with TypeBridge
2.2.1 and requires Rust 1.88+. Offline schema checking, generation, migration
authoring, and planning accept the frozen TypeDB 3.11.5 and 3.12.1 semantic
profiles. Connected migration apply, verify, and adopt require exactly TypeDB
3.12.1.

[Repository](https://github.com/ds1sqe/type-bridge) ·
[API documentation](https://docs.rs/type-bridge-cli/2.2.1) ·
[MIT license](https://github.com/ds1sqe/type-bridge/blob/master/LICENSE)