## Commands

### Analyze

- `./kantra analyze --input=<path/to/source> --output=<path/to/output> --overwrite` --target <target> — Run analysis (containerless mode by default)

- `./kantra analyze --input=... --output=... --run-local=false` — Run analysis in hybrid mode (providers in containers)

### Config 

- `./kantra config login [host] [user] [password]` — Login to Konveyor Hub and store authentication tokens in `~/.kantra/auth.json`

- `./kantra config sync --url=<repo-url> --application-path=<local/app/path>` — Sync Hub application profiles. Downloads profile bundles to `.konveyor/profiles/` in the current directory (default) or `--application-path`

- `./kantra config list [--profile-dir=<path>]` — List local Hub profiles in an application directory (defaults to current directory)
- Add `--insecure` to any config command to skip TLS certificate verification

### Transform openrewrite

- `./kantra transform openrewrite --input=<path> --target=<target>` — Run OpenRewrite recipes

### Provider

- `./kantra provider list` — List available analysis providers (container and containerless)

### Rules

- `./kantra rules list-sources` — List available source technologies from rule labels

- `./kantra rules list-targets` — List available target technologies from rule labels

- `./kantra rules test [paths...]` — Test YAML rules (`--test-filter`, `--prune`, `--run-local`, etc.)


## Test with Koncur

Koncur is a project that can also be used to test kantra changes. It currently works with hybrid mode. 

- See [quickstart](https://github.com/konveyor/koncur/blob/main/README.md#quick-start) for an example of running a kantra test with koncur.
