Skip to content

Commit 44454d1

Browse files
authored
make compilation clear for new users
------- cc: @DCtheGeek
1 parent 60ce7b5 commit 44454d1

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

articles/governance/policy/how-to/guest-configuration-create-linux.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -119,8 +119,7 @@ end
119119

120120
Save this file in a new folder named `controls` inside the `linux-path` directory.
121121

122-
Finally, create a configuration, import the **GuestConfiguration** resource module, and use the
123-
`ChefInSpecResource` resource to set the name of the InSpec profile.
122+
Finally, create a configuration, import the **PSDesiredStateConfiguration** resource module, and compile the configuration.
124123

125124
```powershell
126125
# Define the configuration and import GuestConfiguration
@@ -138,13 +137,18 @@ Configuration AuditFilePathExists
138137
}
139138
140139
# Compile the configuration to create the MOF files
141-
AuditFilePathExists -out ./Config
140+
import-module PSDesiredStateConfiguration
141+
AuditFilePathExists -out ./
142142
```
143+
Save this file with name `config.ps1` in the project folder. Run it in PowerShell by executing `./config.ps1`
144+
in the terminal. A new mof file will be created.
143145

144146
The `Node AuditFilePathExists` command isn't technically required but it produces a file named
145147
`AuditFilePathExists.mof` rather than the default, `localhost.mof`. Having the .mof file name follow
146148
the configuration makes it easy to organize many files when operating at scale.
147149

150+
151+
148152
You should now have a project structure as below:
149153

150154
```file

0 commit comments

Comments
 (0)