From 39acc340126d3b49c567c29c93f1cbab3b5cbc11 Mon Sep 17 00:00:00 2001 From: Mark Bolwell Date: Mon, 20 Nov 2023 14:10:32 +0000 Subject: [PATCH] updated layout Signed-off-by: Mark Bolwell --- docs/source/audit/getting-started-audit.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/source/audit/getting-started-audit.rst b/docs/source/audit/getting-started-audit.rst index a5071f4..da4a7d5 100644 --- a/docs/source/audit/getting-started-audit.rst +++ b/docs/source/audit/getting-started-audit.rst @@ -84,7 +84,7 @@ It is possible to just run the audit on some playbooks (being rolled out across .. code-block:: yaml -audit_only: true + audit_only: true This will run the audit based on the same release as the playbook and will then stop. @@ -92,11 +92,11 @@ Extra variables also enable the ability to copy back the audit output to the con .. code-block:: yaml -# As part of audit_only -# This will enable files to be copied back to control node -fetch_audit_files: false -# Path to copy the files to will create dir structure -audit_capture_files_dir: /some/location to copy to on control node + # As part of audit_only + # This will enable files to be copied back to control node + fetch_audit_files: false + # Path to copy the files to will create dir structure + audit_capture_files_dir: /some/location to copy to on control node Defining the audit