| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Prior to this commit, if you used windows bash git when you clone
down the repo these files would get incorrect permissions which
make them unexecutable.
After this commit, due to some windows bash git magic I don't
understand it appears that adding the shebang to the beginning of
the file causes windows bash git to change the permissions to
so the file is executable.
This resolves https://github.com/puppetlabs/control-repo/issues/40
|
| |\
| |
| | |
Add GitHub instructions
|
| |/
|
| |
Per Issue https://github.com/puppetlabs/control-repo/issues/26
|
| |
|
| |
"Latest" stopped resolving several PE releases ago.
|
| |
|
|
|
|
|
|
|
| |
Prior to this commit, we mitigated issues with hiera-eyaml causing
a memory leak by setting max_requets_per_instance to 0
After this commit, we go back to the default for
max_requests_per_instance because the hiera-eyaml memory leak
has been resolved for months if you use the newest version
|
| |\
| |
| | |
Set the execute bit for CM config version script
|
| |/
|
|
|
|
|
| |
The execute bit needs to be set or CM will fail.
I think this was probably just missed when the
code_manager_config_version.rb file was added.
|
| |\
| |
| | |
Remove old role all_in_one_pe
|
| |/ |
|
| | |
|
| |\
| |
| | |
light editing, mostly for style
|
| |/ |
|
| |\
| |
| | |
Reduce the scope of the control-repo to mostly an example
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Prior to this commit, the control-repo was an example of the
structure of a control repo but it also included puppet code to
help setup code manager and instructions to get that all setup
in a very specific way.
This was great for users that wanted to follow those instructions
exactly but wasn't great for people just looking for an example to
start from.
After this commit, the control-repo will be just an example once
again and a new repo somehwere else will pop up to provide the
explicit instructions on how to use the example with code manager.
There are links added to puppetlabs/control-repo to a new repo
that will have a version of the code that once lived in
puppetlabs/control-repo
|
| |\|
| |
| | |
Move profiles out into their own modules
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Prior to this commit, there was a stash profile in the site dir
of this control-repo.
After this commit, the profile has been moved to it's own repo
where it can be used more generally and not tightly coupled to this
repository.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Prior to this commit, there was a gitlab profile in the site dir
of this control-repo.
After this commit, the profile has been moved to it's own repo
where it can be used more generally and not tightly coupled to this
repository.
As a result, the gitlab role has been removed from this repository
as well.
|
| |/
|
|
|
|
|
|
| |
Prior to this commit, the puppetmaster profile was embedded in this
control-repo.
After this commit, the puppetmaster profile is moved out into its
own module.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Prior to this commit, these two files were laying around but not used.
The code manager template was missed when the code was moved into
a module and the function was added a while ago but then never
put to use.
After this commit, the codebase is a little lighter without these
stale files.
|
| |\
| |
| | |
Move profile::git_webhook into seperate module pe_code_manager_webhook
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Prior to this commit, we were using a pre-release version of the
pe_code_manager_webhook module in order to test that simply
re-namespacing the module form a profile to a module worked as
expected.
After this commit, we use the official 1.0.0 relase of the module
that includes a few changes that make it more versatile.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prior to this commit the functionality to setup the either code
manager or zack/r10k was tightly coupled to this control-repo. In
an effort to make that functionality useful to more people we're
splitting it into a dedicated module.
After this commit, the pe_code_manager_webhook module will contain all logic
around setting up the webhook while this control-repo will still
gloss over the details needed to get everything in PE setup correctly
to use that module.
This commit removes the files associated with the profile including
some custom functions that were only there to make it work.
This commit removes the all_in_one_pe_2015_2 role as it was exactly
the same as the all_in_one_pe role.
This commit modifies all_in_one_pe to use the pe_code_manager_webhook module
instead of the profile.
|
| |\
| |
| | |
Fixed code so hunner/hiera can be pulled from forge
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Disable max-requests-per-instance to mitigate hiera-eyaml mem leak
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| | |
Hiera-eyaml currently causes a memory leak in puppetsever when
max-requests-per-instnace is enabled. So, defaulting to disabling
max-requests-per-instance.
https://tickets.puppetlabs.com/browse/SERVER-1154
https://github.com/TomPoulton/hiera-eyaml/issues/163
|
| |\ \
| | |
| | | |
Corrected documentation grammar.
|
| |/ / |
|
| |\ \
| |/
|/| |
Update all_in_one_pe_2015_2.pp
|
| |/
|
|
| |
Shouldn't this be profile::git_webhook as in all_in_one_pe.pp since the abstraction logic is located there?
Either that or the profile::zack_r10k_webook is missing from the location specified?
|
| |\
| |
| | |
Fix hostname on role creation curl command
|
| |/
|
|
|
|
|
|
|
|
|
| |
Prior to the this commit, if you were using the code_manager
profile on a split install it would incorrectly try to curl the
NC api on the master node.
After this commit, it should correctly curl the hostname of the NC
This has no impact on the functionality of the code on a monolithic
PE installation.
|
| |\
| |
| | |
Move hiera_config to main section of puppet.conf
|
| |/
|
|
|
| |
If it is in master instead of main then puppet apply will give a
warning.
|
| |\
| |
| | |
Changes for PE2015.3.0
|
| | |
| |
| |
| |
| |
| |
| | |
Mostly reorganized the README to be 2015.3 first and then have some
extra info at the bottom about upgrading from 2015.2.
Added a blurb about what the control-repo provides.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Prior to this commit there was a requirement for the user of this
repo to create a RBAC role in order for code manager to work.
After this commit an exec statement will curl the RBAC API to
create the role one time and hopefully it works otherwise the exec
will not run again.
|
