@oneuptime/cli 14.0.96 → 14.0.98
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 +14 -14
- package/build/dist/Index.js +7426 -12977
- package/build/dist/THIRD-PARTY-LICENSES.txt +0 -52
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -11,14 +11,14 @@ oneuptime --version
|
|
|
11
11
|
|
|
12
12
|
The CLI needs Node.js 22 or later. It has no dependencies, so npm installs it without fetching other packages or building anything.
|
|
13
13
|
|
|
14
|
-
|
|
14
|
+
The CLI is released with OneUptime and has the same version number. On a self-hosted OneUptime, install the CLI of your OneUptime's version, so its commands match the records your server has:
|
|
15
15
|
|
|
16
16
|
```bash
|
|
17
|
-
|
|
18
|
-
npm install
|
|
19
|
-
npm start -- --help
|
|
17
|
+
npm install -g @oneuptime/cli@<your-oneuptime-version>
|
|
20
18
|
```
|
|
21
19
|
|
|
20
|
+
> **Warning:** CLI versions before 14.0.64 stop as soon as they start, with an error such as `Cannot find module 'Common/Models/DatabaseModels/Index'`. Install 14.0.64 or later with `npm install -g @oneuptime/cli@latest`. On a self-hosted OneUptime older than 14.0.64, [upgrade OneUptime](https://oneuptime.com/docs/installation/upgrading#how-to-upgrade) first, then install the CLI of the version you upgraded to.
|
|
21
|
+
|
|
22
22
|
## Quick Start
|
|
23
23
|
|
|
24
24
|
```bash
|
|
@@ -208,16 +208,16 @@ Every resource is a command: `oneuptime <resource> <subcommand>`. Resources are
|
|
|
208
208
|
|
|
209
209
|
Records take `list`, `get`, `create`, `update`, `delete` and `count`:
|
|
210
210
|
|
|
211
|
-
| Area | Commands
|
|
212
|
-
| --------------------- |
|
|
213
|
-
| Monitoring | `monitor`, `monitor-status`, `monitor-status-event`
|
|
214
|
-
| Incidents | `incident`, `incident-state`, `incident-severity`, `incident-state-timeline`, `incident-public-note`, `incident-internal-note`, `incident-alert`, `postmortem-status`
|
|
215
|
-
| Alerts | `alert`, `alert-state`, `alert-severity`, `alert-state-timeline`, `alert-internal-note`
|
|
216
|
-
| Status pages | `status-page`, `status-page-announcement`
|
|
217
|
-
| Scheduled maintenance | `scheduled-maintenance-event`, `scheduled-maintenance-state`, `scheduled-maintenance-state-timeline`
|
|
218
|
-
| Teams and on-call | `team`, `on-call-policy`
|
|
219
|
-
| Security | `security-case`, `security-case-note`, `security-case-priority`, `security-case-status`, `security-detection`, `security-playbook`
|
|
220
|
-
| Labels | `label`
|
|
211
|
+
| Area | Commands |
|
|
212
|
+
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
213
|
+
| Monitoring | `monitor`, `monitor-status`, `monitor-status-event` |
|
|
214
|
+
| Incidents | `incident`, `incident-state`, `incident-severity`, `incident-state-timeline`, `incident-public-note`, `incident-internal-note`, `incident-alert`, `postmortem-status` |
|
|
215
|
+
| Alerts | `alert`, `alert-state`, `alert-severity`, `alert-state-timeline`, `alert-internal-note` |
|
|
216
|
+
| Status pages | `status-page`, `status-page-announcement` |
|
|
217
|
+
| Scheduled maintenance | `scheduled-maintenance-event`, `scheduled-maintenance-state`, `scheduled-maintenance-state-timeline` |
|
|
218
|
+
| Teams and on-call | `team`, `on-call-policy` |
|
|
219
|
+
| Security | `security-case`, `security-case-evidence`, `security-case-note`, `security-case-priority`, `security-case-status`, `security-case-task`, `security-detection`, `security-playbook` |
|
|
220
|
+
| Labels | `label` |
|
|
221
221
|
|
|
222
222
|
Telemetry takes `list`, `create` and `count`:
|
|
223
223
|
|