@safetech/inheriti-cli 0.0.25-dev.0 → 0.0.26-dev.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/package.json
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: inheriti-cli
|
|
3
3
|
description: Use the Inheriti® CLI to find, create, inspect, reveal, download, or use protected plans and to configure Business automations from a user's natural-language request.
|
|
4
4
|
metadata:
|
|
5
|
-
version: 0.0.
|
|
5
|
+
version: 0.0.26-dev.0
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Inheriti® CLI
|
|
@@ -8,6 +8,8 @@ When the user identifies their current repository/project folder, derive its Git
|
|
|
8
8
|
|
|
9
9
|
1. `inheriti automations create github --organization ORGANISATION_ID` creates or reuses the **Inheriti connection** only. Optional `--environment` and `--workflow` set the identity; defaults are `inheriti` and `inheriti.yml`. No plan or member belongs to connection creation. Reuse an explicitly selected existing active connection; a disabled match remains disabled, so a fresh connection is created.
|
|
10
10
|
2. `inheriti automations setup github --organization ORGANISATION_ID --connection CONNECTION_ID --plan PLAN_ID --field ASSET.FIELD` prepares technical setup from the connection's stored trust. It previews by default; authorised `--apply` commits the dedicated workflow and verifies identity through GitHub. It never creates a connection or grants plan access. The generated workflow's narrow push trigger registers it in Actions; both jobs are gated to manual dispatch, so that registration run is skipped. The commit can also trigger other existing push workflows in the repository. Pairing starts only through the separate explicit manual dispatch. No manual YAML preparation is needed.
|
|
11
|
+
|
|
12
|
+
During `--apply`, an interactive terminal shows the current setup step, elapsed time, and a GitHub run link once available. Redirected output shows one plain line per step. If pairing remains pending, rerun the same command to resume the saved attempt; do not dispatch a second job manually.
|
|
11
13
|
3. After `VERIFIED`, use the separate `automations grant create --organization ORGANISATION_ID` and `grant activate --organization ORGANISATION_ID` commands with the selected plan, connection and responsible member. Preserve the same grant ID on retries: create succeeds again only when that exact ID, connection and member already have a `PENDING_VERIFICATION` or `ACTIVE` grant; activation succeeds again only when that exact grant is `ACTIVE`. Conflicting grants still need review. Let Business validate eligibility.
|
|
12
14
|
4. Only after access is active, the generated workflow can run normally. The protected plan's usual SafeKey Mobile approval may still be required during that run. Do not dispatch protected usage merely to prove setup. Resolve its filename from the selected connection's trust, not unrelated creation-field state.
|
|
13
15
|
|
package/skill/manifest.json
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"schema":1,"cliVersion":"0.0.
|
|
1
|
+
{"schema":1,"cliVersion":"0.0.26-dev.0","deployment":"dev","sha256":"659ea4497fe55c1e1a4cea018096277a2e11f5b6b62bb5a5cba0e98490864ded"}
|