| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
- Moved ssh key generation and git deploy key out of the puppetmaster
profile and into zack_r10k and code_manager
- Swapped code manager into the all_in_one role
- Made a 2015.2 all_in_one role if users prefer to use it
- Conditionally move all existing code out of environmentpath
to allow file sync to sync files
- Update the README to compliment the new puppet code
|
| |
|
|
|
|
|
|
|
|
| |
Moved the webhook resource out of puppetmaster and into zack_r10k
to support exchaning code_manager in place of zack_r10k
As a result I cleaned up some unnecessary parameters.
Installing both the r10k webhook and the code_manager at this time
for testing
|
| |\
| |
| |
| | |
merge_npwalker_control_repo
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Previously there was a mcollective and no_mcollective version of
the webhook profile. They were almost identical so I merged them
and manage the difference with a "use_mcollective" parameter.
I renamed the webhook profile to zack_r10k_webhook.
|
| | |
| |
| |
| |
| |
| |
| | |
To accomodate generating random usernames and passwords, I had
to parameterize the profiles which I didn't feel great about
but I also didn't want to have to put the username and pass in
hiera.
|
| | |
| |
| |
| |
| |
| | |
In order to complete the change I refactered the webhook into
its own set of profiles, one with mcollective and the other
without.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Updating README for instructions on how to use the control-repo
by putting it in your own git server and then using the r10k
answers during installation of PE.
Removing the manifest for configuring r10k using zack/r10k.
Added a role that can be used to bootstrap an all-in-one PE
installation.
|
| | |
|
| |
|
