From c56f40a219f25dc367697d2b8f423a802923f2cf Mon Sep 17 00:00:00 2001 From: Begona Guereca Date: Mon, 15 Aug 2022 12:22:01 -0700 Subject: [PATCH] Update jenkins/valet-audit-lab.md Co-authored-by: j-dunham --- jenkins/valet-audit-lab.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jenkins/valet-audit-lab.md b/jenkins/valet-audit-lab.md index 6afb0a0..229c722 100644 --- a/jenkins/valet-audit-lab.md +++ b/jenkins/valet-audit-lab.md @@ -21,7 +21,7 @@ By the end of this lab you will have performed an audit on the demo Jenkins inst We will be performing an audit against a preconfigured Jenkins instance. Before running the command we need to collect some information: - 1. Do we want to audit the entire Jenkins instance, or just a single folder? __In this example we will be auditing the entire Jenkins instance, but in the future if you wanted to configure a specific folder to be audited add the `-f flag to the audit command__ + 1. Do we want to audit the entire Jenkins instance, or just a single folder? __In this example we will be auditing the entire Jenkins instance, but in the future if you wanted to configure a specific folder to be audited add the `-f ` flag to the audit command__ 2. Where do we want to store the result? __./tmp/audit. This can be any valid path on the system. In the case of codespaces it is generally best to use `./tmp/SOME_DIRECTORY_HERE` so the files show in explorer__ ### Steps