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
Copy file name to clipboardExpand all lines: README.md
+93-19Lines changed: 93 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,44 +1,47 @@
1
1
# Node Scraper
2
-
Node Scraper is a tool which performs automated data collection and analysis for the purposes of system debug.
2
+
Node Scraper is a tool which performs automated data collection and analysis for the purposes of
3
+
system debug.
3
4
4
5
## Installation
5
6
### Install From Source
6
-
Node Scraper requires Python 3.10+ for installation. After cloning this repository, call dev-setup.sh script with 'source'. This script creates an editable install of Node Scraper in a python virtual environment and also configures the pre-commit hooks for the project.
7
+
Node Scraper requires Python 3.10+ for installation. After cloning this repository,
8
+
call dev-setup.sh script with 'source'. This script creates an editable install of Node Scraper in
9
+
a python virtual environment and also configures the pre-commit hooks for the project.
7
10
8
11
```sh
9
12
source dev-setup.sh
10
13
```
11
14
12
15
## CLI Usage
13
-
The Node Scraper CLI can be used to run Node Scraper plugins on a target system. The following CLI options are available:
16
+
The Node Scraper CLI can be used to run Node Scraper plugins on a target system. The following CLI
Specify system interaction level, used to determine the type of actions that plugins can perform (default: INTERACTIVE)
37
40
--sys-sku STRING Manually specify SKU of system (default: None)
38
41
--sys-platform STRING
39
42
Specify system platform (default: None)
40
-
--plugin-config STRING
41
-
Path to plugin config json (default: None)
43
+
--plugin-configs [STRING ...]
44
+
built-in config names or paths to plugin config JSONs. Available built-in configs: NodeStatus (default: None)
42
45
--system-config STRING
43
46
Path to system config json (default: None)
44
47
--connection-config STRING
@@ -49,7 +52,8 @@ options:
49
52
50
53
```
51
54
52
-
The plugins to run can be specified in two ways, using a plugin JSON config file or using the 'run-plugins' sub command. These two options are not mutually exclusive and can be used together.
55
+
The plugins to run can be specified in two ways, using a plugin JSON config file or using the
56
+
'run-plugins' sub command. These two options are not mutually exclusive and can be used together.
A plugin JSON config should follow the structure of the plugin config model defined here. The globals field is a dictionary of global key-value pairs; values in globals will be passed to any plugin that supports the corresponding key. The plugins field should be a dictionary mapping plugin names to sub-dictionaries of plugin arguments. Lastly, the result_collators attribute is used to define result collator classes that will be run on the plugin results. By default, the CLI adds the TableSummary result collator, which prints a summary of each plugin’s results in a tabular format to the console.
87
+
A plugin JSON config should follow the structure of the plugin config model defined here.
88
+
The globals field is a dictionary of global key-value pairs; values in globals will be passed to
89
+
any plugin that supports the corresponding key. The plugins field should be a dictionary mapping
90
+
plugin names to sub-dictionaries of plugin arguments. Lastly, the result_collators attribute is
91
+
used to define result collator classes that will be run on the plugin results. By default, the CLI
92
+
adds the TableSummary result collator, which prints a summary of each plugin’s results in a
93
+
tabular format to the console.
84
94
85
95
```json
86
96
{
@@ -101,13 +111,15 @@ A plugin JSON config should follow the structure of the plugin config model defi
101
111
```
102
112
103
113
### 'gen-plugin-config' sub command
104
-
The 'gen-plugin-config' sub command can be used to generate a plugin config JSON file for a plugin or list of plugins that can then be customized. Plugin arguments which have default values will be prepopulated in the JSON file, arguments without default values will have a value of 'null'.
114
+
The 'gen-plugin-config' sub command can be used to generate a plugin config JSON file for a plugin
115
+
or list of plugins that can then be customized. Plugin arguments which have default values will be
116
+
prepopulated in the JSON file, arguments without default values will have a value of 'null'.
@@ -134,9 +146,12 @@ This would produce the following config:
134
146
```
135
147
136
148
### 'run-plugins' sub command
137
-
The plugins to run and their associated arguments can also be specified directly on the CLI using the 'run-plugins' sub-command. Using this sub-command you can specify a plugin name followed by the arguments for that particular plugin. Multiple plugins can be specified at once.
149
+
The plugins to run and their associated arguments can also be specified directly on the CLI using
150
+
the 'run-plugins' sub-command. Using this sub-command you can specify a plugin name followed by
151
+
the arguments for that particular plugin. Multiple plugins can be specified at once.
138
152
139
-
You can view the available arguments for a particular plugin by running `node-scraper run-plugins <plugin-name> -h`:
153
+
You can view the available arguments for a particular plugin by running
0 commit comments