summaryrefslogtreecommitdiffstats
path: root/docs/cli
diff options
context:
space:
mode:
Diffstat (limited to 'docs/cli')
-rw-r--r--docs/cli/inv-from-cvp.md27
-rw-r--r--docs/cli/nrfu.md18
2 files changed, 28 insertions, 17 deletions
diff --git a/docs/cli/inv-from-cvp.md b/docs/cli/inv-from-cvp.md
index 8897370..a37af62 100644
--- a/docs/cli/inv-from-cvp.md
+++ b/docs/cli/inv-from-cvp.md
@@ -8,21 +8,32 @@
In large setups, it might be beneficial to construct your inventory based on CloudVision. The `from-cvp` entrypoint of the `get` command enables the user to create an ANTA inventory from CloudVision.
+!!! info
+ The current implementation only works with on-premises CloudVision instances, not with CloudVision as a Service (CVaaS).
+
### Command overview
```bash
-anta get from-cvp --help
Usage: anta get from-cvp [OPTIONS]
- Build ANTA inventory from Cloudvision
+ Build ANTA inventory from CloudVision.
+
+ NOTE: Only username/password authentication is supported for on-premises CloudVision instances.
+ Token authentication for both on-premises and CloudVision as a Service (CVaaS) is not supported.
Options:
- -ip, --cvp-ip TEXT CVP IP Address [required]
- -u, --cvp-username TEXT CVP Username [required]
- -p, --cvp-password TEXT CVP Password / token [required]
- -c, --cvp-container TEXT Container where devices are configured
- -d, --inventory-directory PATH Path to save inventory file
- --help Show this message and exit.
+ -o, --output FILE Path to save inventory file [env var: ANTA_INVENTORY;
+ required]
+ --overwrite Do not prompt when overriding current inventory [env
+ var: ANTA_GET_FROM_CVP_OVERWRITE]
+ -host, --host TEXT CloudVision instance FQDN or IP [required]
+ -u, --username TEXT CloudVision username [required]
+ -p, --password TEXT CloudVision password [required]
+ -c, --container TEXT CloudVision container where devices are configured
+ --ignore-cert By default connection to CV will use HTTPS
+ certificate, set this flag to disable it [env var:
+ ANTA_GET_FROM_CVP_IGNORE_CERT]
+ --help Show this message and exit.
```
The output is an inventory where the name of the container is added as a tag for each host:
diff --git a/docs/cli/nrfu.md b/docs/cli/nrfu.md
index 76605cb..90b4a40 100644
--- a/docs/cli/nrfu.md
+++ b/docs/cli/nrfu.md
@@ -67,7 +67,7 @@ Options:
```bash
anta nrfu --device DC1-LEAF1A text
```
-[![anta nrfu text results](../imgs/anta-nrfu-text-output.png){ loading=lazy width="1600" }](../imgs/anta-nrfu-text-output.png)
+![anta nrfu text results](../imgs/anta-nrfu-text-output.png){ loading=lazy width="1600" }
## Performing NRFU with table rendering
@@ -92,31 +92,31 @@ The `--group-by` option show a summarized view of the test results per host or p
```bash
anta nrfu --tags LEAF table
```
-[![anta nrfu table results](../imgs/anta-nrfu-table-output.png){ loading=lazy width="1600" }](../imgs/anta-nrfu-table-output.png)
+![anta nrfu table results](../imgs/anta-nrfu-table-output.png){ loading=lazy width="1600" }
For larger setups, you can also group the results by host or test to get a summarized view:
```bash
anta nrfu table --group-by device
```
-[![anta nrfu table group_by_host_output](../imgs/anta-nrfu-table-group-by-host-output.png){ loading=lazy width="1600" }](../imgs/anta-nrfu-table-group-by-host-output.png)
+![$1anta nrfu table group_by_host_output](../imgs/anta-nrfu-table-group-by-host-output.png){ loading=lazy width="1600" }
```bash
anta nrfu table --group-by test
```
-[![anta nrfu table group_by_test_output](../imgs/anta-nrfu-table-group-by-test-output.png){ loading=lazy width="1600" }](../imgs/anta-nrfu-table-group-by-test-output.png)
+![$1anta nrfu table group_by_test_output](../imgs/anta-nrfu-table-group-by-test-output.png){ loading=lazy width="1600" }
To get more specific information, it is possible to filter on a single device or a single test:
```bash
anta nrfu --device spine1 table
```
-[![anta nrfu table filter_host_output](../imgs/anta-nrfu-table-filter-host-output.png){ loading=lazy width="1600" }](../imgs/anta-nrfu-table-filter-host-output.png)
+![$1anta nrfu table filter_host_output](../imgs/anta-nrfu-table-filter-host-output.png){ loading=lazy width="1600" }
```bash
anta nrfu --test VerifyZeroTouch table
```
-[![anta nrfu table filter_test_output](../imgs/anta-nrfu-table-filter-test-output.png){ loading=lazy width="1600" }](../imgs/anta-nrfu-table-filter-test-output.png)
+![$1anta nrfu table filter_test_output](../imgs/anta-nrfu-table-filter-test-output.png){ loading=lazy width="1600" }
## Performing NRFU with JSON rendering
@@ -143,7 +143,7 @@ The `--output` option allows you to save the JSON report as a file.
```bash
anta nrfu --tags LEAF json
```
-[![anta nrfu json results](../imgs/anta-nrfu-json-output.png){ loading=lazy width="1600" }](../imgs/anta-nrfu-json-output.png)
+![$1anta nrfu json results](../imgs/anta-nrfu-json-output.png){ loading=lazy width="1600" }
## Performing NRFU with custom reports
@@ -173,7 +173,7 @@ The `--output` option allows you to choose the path where the final report will
```bash
anta nrfu --tags LEAF tpl-report --template ./custom_template.j2
```
-[![anta nrfu tpl_resultss](../imgs/anta-nrfu-tpl-report-output.png){ loading=lazy width="1600" }](../imgs/anta-nrfu-tpl-report-output.png)
+![$1anta nrfu tpl_results](../imgs/anta-nrfu-tpl-report-output.png){ loading=lazy width="1600" }
The template `./custom_template.j2` is a simple Jinja2 template:
@@ -205,4 +205,4 @@ cat nrfu-tpl-report.txt
It is possible to run `anta nrfu --dry-run` to execute ANTA up to the point where it should communicate with the network to execute the tests. When using `--dry-run`, all inventory devices are assumed to be online. This can be useful to check how many tests would be run using the catalog and inventory.
-[![anta nrfu dry_run](../imgs/anta_nrfu___dry_run.svg){ loading=lazy width="1600" }](../imgs/anta_nrfu___dry_run.svg)
+![$1anta nrfu dry_run](../imgs/anta_nrfu___dry_run.svg){ loading=lazy width="1600" }