@@ -134,15 +134,6 @@ Determine if all p2p conenctions defined in graph are established
134134Bring down a running warnet
135135
136136
137- ### ` warcli network generate-yaml `
138- Generate a Kubernetes YAML file from a graph file for deploying warnet nodes.
139-
140- options:
141- | name | type | required | default |
142- | ------------| --------| ------------| ----------------------------------|
143- | graph_file | Path | | resources/graphs/default.graphml |
144- | output | String | | "warnet-deployment.yaml" |
145-
146137### ` warcli network logs `
147138Get Kubernetes logs from the RPC server
148139
@@ -152,21 +143,6 @@ options:
152143| follow | Bool | | False |
153144
154145### ` warcli network start `
155- Start a warnet with topology loaded from a \< graph_file>
156-
157- options:
158- | name | type | required | default |
159- | ------------| --------| ------------| ----------------------------------|
160- | graph_file | Path | | resources/graphs/default.graphml |
161- | logging | Bool | | False |
162-
163- ### ` warcli network status `
164- Return pod status
165-
166-
167- ## Network2
168-
169- ### ` warcli network2 start2 `
170146Start a warnet with topology loaded from \< network_name> into [ network]
171147
172148options:
@@ -176,6 +152,10 @@ options:
176152| network | String | | "warnet" |
177153| logging | Bool | | False |
178154
155+ ### ` warcli network status `
156+ Return pod status
157+
158+
179159## Scenarios
180160
181161### ` warcli scenarios active `
0 commit comments