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: Ansible/snapmirror_report/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ The output of the report is a CSV file with the following columns:
16
16
There are three files used to create the report:
17
17
-`generate_report.yaml`: The Ansible playbook that generates the report.
18
18
-`processs_region.yaml`: A collection of tasks that will process all the FSxNs in a region.
19
-
-`get_all_fsxn_regions.yaml`: A colleciton of tasks that retrieves all the regions, that are enabled for the account, where FSx for ONTAP is available.
19
+
-`get_all_fsxn_regions.yaml`: A collection of tasks that retrieves all the regions, that are enabled for the account, where FSx for ONTAP is available.
20
20
21
21
You will also need to create a file named (by default) `secrets_list.csv` that list the secret name for each FSx file system.
22
22
The format of the file should be:
@@ -26,7 +26,7 @@ file_system_id,secret_name
26
26
You should have all four of these files in a single directory.
27
27
28
28
## Configuration
29
-
There are a few varaibles that can be changed at the top of the `generate_report.yaml` file:
29
+
There are a few variables that can be changed at the top of the `generate_report.yaml` file:
30
30
- report\_name - Sets the file path of the report that will be generated.
31
31
- secrets\_list\_file - Sets the file path of the file that contains the list of FSx file systems and their secrets.
32
32
- secrets\_region - Set the region where the secrets are stored.
@@ -36,7 +36,7 @@ To generate the report, run the following command:
36
36
```bash
37
37
ansible-playbook generate_report.yaml
38
38
```
39
-
After a succesful run, the report will be saved to the file path specified in the `report_name` variable.
39
+
After a successful run, the report will be saved to the file path specified in the `report_name` variable.
0 commit comments