@tarileo/avileo-catalog-cli 0.2.2 → 0.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +24 -8
- package/dist/index.js +759 -193
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
# @tarileo/avileo-catalog-cli
|
|
2
2
|
|
|
3
|
-
The Avileo tenant-agent command line interface for a registered
|
|
3
|
+
The Avileo tenant-agent command line interface for a registered business with effective catalog-agent access.
|
|
4
4
|
|
|
5
5
|
For a first-time human connection, use the temporary device authorization link:
|
|
6
6
|
|
|
7
7
|
```sh
|
|
8
|
-
npx --yes @tarileo/avileo-catalog-cli@0.
|
|
8
|
+
npx --yes @tarileo/avileo-catalog-cli@0.3.1 auth login --json
|
|
9
9
|
```
|
|
10
10
|
|
|
11
11
|
The CLI prints only the verification URI, user code and status, opens the link
|
|
@@ -15,7 +15,15 @@ in the URL. Use `auth status --json` to inspect the source (`environment` or
|
|
|
15
15
|
`local`) without revealing the key, and `auth logout --json` to remove only the
|
|
16
16
|
local credential; remote revocation remains an Avileo action.
|
|
17
17
|
|
|
18
|
-
|
|
18
|
+
If Avileo has already issued an Agent Key, configure it without putting the
|
|
19
|
+
secret in shell history, process arguments or JSON:
|
|
20
|
+
|
|
21
|
+
```sh
|
|
22
|
+
avileo auth configure --json
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
The command reads the key without echoing it and stores it locally. For CI/CD
|
|
26
|
+
and automated agents, continue injecting `AVILEO_AGENT_API_KEY`.
|
|
19
27
|
Environment credentials always take priority over the local credential file.
|
|
20
28
|
Never pass an Agent Key through flags, prompts or JSON input.
|
|
21
29
|
|
|
@@ -29,8 +37,16 @@ reference for headers, idempotency, resources and errors.
|
|
|
29
37
|
|
|
30
38
|
For operators and AI agents, the recommended sequence is:
|
|
31
39
|
|
|
32
|
-
1. Run `business show --json
|
|
33
|
-
2.
|
|
34
|
-
3.
|
|
35
|
-
4.
|
|
36
|
-
5.
|
|
40
|
+
1. Run `business show --json` to confirm the connected business and actions.
|
|
41
|
+
2. Run `business profile show --json` when evaluating profile completeness.
|
|
42
|
+
3. Read the exact catalog resource before proposing a change.
|
|
43
|
+
4. Run direct mutations without `--apply` to review local validation or a diff.
|
|
44
|
+
5. Add `--apply` to create a proposal; this does not mutate the business.
|
|
45
|
+
6. Ask the human to approve the exact proposal in Avileo, then apply the
|
|
46
|
+
returned operation or approval ID.
|
|
47
|
+
7. Use the durable import preview/apply flow for structured supplier lists.
|
|
48
|
+
|
|
49
|
+
Profile updates use a direct JSON object with `business profile update --from
|
|
50
|
+
profile-update.json`. Without `--apply` the command returns a local diff; with
|
|
51
|
+
`--apply` it creates a `business.profile.update` proposal. After approval, run
|
|
52
|
+
`operation apply <id> --json` and re-read the profile.
|