| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
Prior to this, the config_version script just showed the commit ID of
the version of code being compiled. This commit includes the compiling
Puppet master's hostname and environment name in the config_version.
This is very useful for debugging when a Puppet master is failing and
you have multiple masters behind a load balancer.
The output of config_version now looks like this:
pupmaster01-production-ac9785273a10
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Update config_version.sh to read the r10k_deploy.json file if it
exists. If it does not exist it will fall back to the existing
logic
|
| | |
|
| | |
|
| | |
|
| |
|
