Commit 61ae61d7 authored by Cool Fire's avatar Cool Fire
Browse files

Added example to run for testing purposes

parent e0d43936
Pipeline #623 passed with stages
in 8 minutes and 8 seconds
......@@ -127,7 +127,7 @@ GREAT! That's finally all we need to do to start testing stuff in vagrant. We'll
## Testing puppet code inside vagrant
Now that we've spent an hour setting up a vagrant box, let's test some code! Run `vagrant up` to start your VM, then run `vagrant provision` to have puppet provision the VM. Exciting! But it doesn't seem to do much yet. This is because we've not told it to do anything yet so we'll include a profile. Edit the "manifests/default.pp" file to `include ::role::something` or `::profile::something` you are working on. From this point onward you should be ready to write and test your puppet code!
Now that we've spent an hour setting up a vagrant box, let's test some code! Run `vagrant up` to start your VM, then run `vagrant provision` to have puppet provision the VM. Exciting! But it doesn't seem to do much yet. This is because we've not told it to do anything yet so we'll include a profile. Edit the "manifests/default.pp" file to `include ::role::something` or `::profile::something` you are working on. You can try `include ::role::base` to test right now. Run `vagrant provision` again and you should see puppet making changes for you. From this point onward you should be ready to write and test your puppet code!
If you are missing any of the standard puppet libraries, you can install them using librarian-puppet
```
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment