You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specify system interaction level, used to determine the type of actions that plugins can perform (default:
43
-
INTERACTIVE)
41
+
Specify system interaction level, used to determine the type of actions that plugins can perform (default: INTERACTIVE)
44
42
--sys-sku STRING Manually specify SKU of system (default: None)
45
43
--sys-platform STRING
46
44
Specify system platform (default: None)
@@ -55,9 +53,43 @@ options:
55
53
Change python log level (default: INFO)
56
54
--gen-reference-config
57
55
Generate reference config from system. Writes to ./reference_config.json. (default: False)
56
+
--skip-sudo Skip plugins that require sudo permissions (default: False)
58
57
59
58
```
60
59
60
+
### Execution Methods
61
+
62
+
Node Scraper can operate in two modes: LOCAL and REMOTE, determined by the `--sys-location` argument.
63
+
64
+
- **LOCAL** (default): Node Scraper is installed and run directly on the target system. All data collection and plugin execution occur locally.
65
+
- **REMOTE**: Node Scraper runs on your local machine but targets a remote system over SSH. In this mode, Node Scraper does not need to be installed on the remote system; all commands are executed remotely via SSH.
66
+
67
+
To use remote execution, specify `--sys-location REMOTE` and provide a connection configuration file with `--connection-config`.
- If using SSH keys, specify `key_filename` instead of `password`.
91
+
- The remote user must have permissions to run the requested plugins and access required files. If needed, use the `--skip-sudo` argument to skip plugins requiring sudo.
92
+
61
93
### Subcommmands
62
94
63
95
Plugins to run can be specified in two ways, using a plugin JSON config file or using the
0 commit comments