@drip-apex/apex-cli 0.3.0 → 0.4.0
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 +18 -0
- package/dist/cli.js +2051 -900
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,5 +1,23 @@
|
|
|
1
1
|
# Apex CLI
|
|
2
2
|
|
|
3
|
+
## Authentication and context
|
|
4
|
+
|
|
5
|
+
Run `apex login` once to authenticate your account. Interactive login opens
|
|
6
|
+
the browser and then lets you select an organization and shop. Inspect the
|
|
7
|
+
credential and every accessible context with `apex whoami`, and switch the
|
|
8
|
+
stored default with `apex use <org>[/<shop>]` (IDs and unambiguous name
|
|
9
|
+
prefixes are accepted).
|
|
10
|
+
|
|
11
|
+
Every command also accepts `--org <id>` and `--shop <id>`. Their precedence is
|
|
12
|
+
command flag, then `DRIP_ORG` / `DRIP_SHOP`, then the context saved by
|
|
13
|
+
`apex use`. JSON envelopes echo the effective org, shop, and credential kind.
|
|
14
|
+
|
|
15
|
+
Automation should continue injecting a narrow shop key per process with
|
|
16
|
+
`DRIP_API_KEY`; it takes precedence over a stored user credential and does not
|
|
17
|
+
change the stored login. Use `apex login --api-key apx_uk_...` for a headless
|
|
18
|
+
account login or `apex login --api-key apx_...` to store a shop key. The old
|
|
19
|
+
`apex login --user` spelling is a deprecated alias for `apex login`.
|
|
20
|
+
|
|
3
21
|
Command-line tools for Apex experiments, draft workspaces, GitOps pushes, QA
|
|
4
22
|
evidence, tracking checks, and agent handoffs.
|
|
5
23
|
|