@automatify-au/cli 0.1.14 → 0.1.16
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 +17 -3
- package/dist/automatify.cjs +1301 -257
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -77,15 +77,25 @@ Minimum:
|
|
|
77
77
|
- `TESTOPS_FORGE_ENDPOINT` for commands that call Forge contracts (`doctor`, `ingest`, `run`, `sync`)
|
|
78
78
|
- `TESTOPS_FORGE_AUTH_TOKEN` from the one-time token shown in Forge `Operations -> CLI access`
|
|
79
79
|
|
|
80
|
-
Local
|
|
80
|
+
Local Jira auth helper on macOS/Windows:
|
|
81
|
+
```bash
|
|
82
|
+
printf "%s" "$JIRA_API_TOKEN" | automatify testops auth login \
|
|
83
|
+
--base-url https://automatify-com-au.atlassian.net \
|
|
84
|
+
--jira-email you@example.com \
|
|
85
|
+
--token-stdin
|
|
86
|
+
automatify testops auth status
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
On Linux/CI, keep `JIRA_API_TOKEN` in the environment and run `auth login` without `--token-stdin`; the CLI stores only non-secret Jira settings. Use `automatify testops auth logout` to remove local Jira and Forge credentials while preserving non-secret URL/email settings. Environment variables are not modified by logout.
|
|
90
|
+
|
|
91
|
+
Forge transport auth remains an advanced setting:
|
|
81
92
|
```bash
|
|
82
|
-
automatify testops config set baseUrl https://automatify-com-au.atlassian.net
|
|
83
93
|
automatify testops config set projectKey DEV
|
|
84
94
|
automatify testops config set forgeEndpoint "<webtrigger-url>"
|
|
85
95
|
printf "%s" "$TESTOPS_FORGE_AUTH_TOKEN" | automatify testops config set forgeAuthToken --stdin
|
|
86
96
|
```
|
|
87
97
|
|
|
88
|
-
|
|
98
|
+
Jira and Forge secrets use macOS Keychain on macOS and current-user Windows DPAPI on Windows. Linux and CI keep secrets in `JIRA_API_TOKEN` and `TESTOPS_FORGE_AUTH_TOKEN`. Existing plaintext local tokens remain readable for compatibility and can be migrated with `automatify testops config migrate-secrets`. See [AUTH.md](./AUTH.md) for the normal Jira auth workflow and [WINDOWS.md](./WINDOWS.md) for PowerShell setup and verification.
|
|
89
99
|
|
|
90
100
|
Optional:
|
|
91
101
|
- `TESTOPS_FORGE_TIMEOUT_MS`
|
|
@@ -114,6 +124,10 @@ All TestOps commands are invoked as `automatify testops <command>`:
|
|
|
114
124
|
- `automatify testops bdd features export --output-dir ./features-export --feature-id <FEATURE_ID>`
|
|
115
125
|
- `runs`
|
|
116
126
|
- `automatify testops runs show --id <RUN_ID>`
|
|
127
|
+
- `auth`
|
|
128
|
+
- `automatify testops auth login --base-url <JIRA_URL> --jira-email <EMAIL> --token-stdin`
|
|
129
|
+
- `automatify testops auth status`
|
|
130
|
+
- `automatify testops auth logout`
|
|
117
131
|
- `config`
|
|
118
132
|
- `automatify testops config show`
|
|
119
133
|
- `automatify testops config validate`
|