Skip to content

puppetlabs/control-repo-vagrant

 
 

Repository files navigation

#One-time Setup

The first time you use this stack you need to setup the puppetlabs/control-repo in your gitlab server.

Outline of steps:

  1. vagrant up puppet-master-201621; vagrant up gitlab-server
  2. Login into the gitlab UI via the ip address assigned to your vagrant instance
  • I recommend added this to your local hosts file so you can easily access the interface in the future
  1. Follow the instructions in puppetlabs/control-repo to get everything setup in gitlab
  1. Once you have completed these steps I recommend snapshotting the gitlab server so you can always get back to this state

How to use this stack

This stack bootstraps itself by

  1. Installing with an answer file that configures r10k/code manager to connect to the puppet/control-repo on the local gitlab server
  2. Running r10k
  3. Using the pe_code_manager_webhook module to set everything up and then running puppet a few more times

This Vagrant Stack is Based on the puppet-debugging-kit

Please follow the setup instructions for the debugging kit before cloning down this repo.

https://github.com/Sharpie/puppet-debugging-kit

About

A Vagrant Stack For Testing Install of PE with npwalker/control-repo

Resources

Code of conduct

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Ruby 81.9%
  • Shell 10.7%
  • Puppet 7.4%