gtme adapters
List installed adapters with their source and pin (.source.json)
What you'll learn
You're about to type gtme adapters and want its forms and its flags.
- every form of
gtme adaptersand what each does - each flag and what it changes
- where the docs use it
List installed adapters with their source and pin (.source.json)
Forms
gtme adapters
gtme adapters search TEXT
gtme adapters add REF...
gtme adapters verify ID
gtme adapters update ID [@ref]
| Form | Does |
|---|---|
gtme adapters | list installed adapters with their source and pin (.source.json) |
gtme adapters search TEXT | search the bindings registry index by id, vendor, description and role (GTME_REGISTRY overrides the index URL) |
gtme adapters add REF... | install bindings by github.com/<owner>/<repo>/<path>[@ref] or registry id (apollo/search), each pinned and verified first (schema + fixtures offline; nothing installs unverified), under ~/.gtme/adapters/ with .source.json beside it; every vendor adapter but instantly/ installs this way |
gtme adapters verify ID | validate an installed binding against the schema, run its fixtures offline, print the hosts it will call and the credentials it will demand |
gtme adapters update ID [@ref] | re-fetch at a newer ref — the only thing that moves a pin |
It exits with one of the exit codes every verb shares.
Example
From Add a vendor:
gtme adapters search jsonplaceholder
Used in
- Two adapter tiers: The search, add, verify, and update verbs
- Connect your stack: secrets, plan, dry-run, arm: The search, add, verify, and update verbs
- Add a vendor with a binding: The verify verb this guide runs until it passes, and the verbs that install from the registry
- Write a process adapter: Lists installed adapters with their kind and source
- Publish to the registry: The search, add, verify, and update verbs this guide runs