From 0134322e73602de0cc7dbfb71f9561d549e645f4 Mon Sep 17 00:00:00 2001 From: Amndeep Singh Mann Date: Fri, 20 Dec 2024 03:21:26 -0500 Subject: [PATCH] shivani's suggestion that we actually use good practices and pedagogy Signed-off-by: Amndeep Singh Mann --- src/courses/advanced/05.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/courses/advanced/05.md b/src/courses/advanced/05.md index bcade6b67..80d85722d 100644 --- a/src/courses/advanced/05.md +++ b/src/courses/advanced/05.md @@ -46,8 +46,8 @@ This will generate a `git_test_target` repository which we will use for these ex Now let's write some tests and confirm that they run. You can put these tests in the `example.rb` file generated in the `controls` folder of your `my_git` InSpec profile. These tests are written using the `command` resource which is provided by InSpec. We will write a `git` resource in this section to improve this test. -::: note Input review -You will need to put the full directory path of the `.git` file from your `git_test_target` repository as the value for the `git_dir` input in your `inspec.yml`. To get the full path of your current location in the terminal, use `pwd`. The value in the codeblock below should be correct, but it's always good to doublecheck. +::: note Inputs review +The `git_dir` input will be used in our profile. It needs to contain the path of the `.git` folder you are assessing. Usually, you'd want to put a default location for that input in your `inspec.yml`, such as `./.git`, that the user of your profile could overwrite with an inputfile, but for expediency's sake we're going to hardcode it to the `.git` folder inside of your `git_test_target` repository. The value in the codeblock below should be correct, but it's always good to doublecheck by using the `cd` command to navigate inside of the `.git` folder in the `git_test_target` repository and then using the `pwd` command to get the full path. ::: ::: code-tabs