greentic-cards2pack 0.4.2

Generate Greentic pack workspaces and archives from Adaptive Cards
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
60
61
62

# greentic-cards2pack

Generate Greentic pack workspaces and `.gtpack` archives from a directory of Adaptive Card JSON files.

This CLI scans cards, groups them into flows, generates flow files, and packages everything into a Greentic pack in a single command.

## Quick Start

1) Install:

```bash
cargo install cargo-binstall 
cargo binstall greentic-cards2pack
```

You also need:

```bash
cargo binstall greentic-flow greentic-pack
```

2) Run:

```bash
greentic-cards2pack generate \
  --cards ./cards \
  --out ./packs/hr-demo \
  --name hr-demo
```

## What You Get

`--out` becomes a full pack workspace:

```
./packs/hr-demo/
  pack.yaml
  flows/main.ygtc
  assets/cards/...
  dist/hr-demo.gtpack
  .cards2pack/manifest.json
```

The generated flow uses the Adaptive Card component:
`oci://ghcr.io/greentic-ai/components/component-adaptive-card:latest`.

## Common Warnings

- `ignored_file`: A JSON file under `--cards` is not an Adaptive Card (missing `type: "AdaptiveCard"`).
  - Safe to ignore if those JSON files are supporting data.
  - If it should be a card, fix the file so it has `type: "AdaptiveCard"`.

- `missing_target`: A card action references a step/cardId that does not exist in the flow.
  - In non-strict mode, a stub node is created.
  - In strict mode, this is an error and generation fails.
  - Fix by ensuring the target card exists or updating the action data.

## Tips

- Use `--strict` to enforce consistent metadata and required targets.
- The `.cards2pack/manifest.json` file records the scan results and warnings.