Skip to content

Commit

Permalink
shivani's suggestion that we actually use good practices and pedagogy
Browse files Browse the repository at this point in the history
Signed-off-by: Amndeep Singh Mann <[email protected]>
  • Loading branch information
Amndeep7 committed Dec 20, 2024
1 parent a01c1a2 commit 0134322
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions src/courses/advanced/05.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 0134322

Please sign in to comment.