control-repo-template/scripts, branch 1.1.0puppetlabs/control-repo extended with not-so-core stuffhttps://git.pfeiffer.tech/control-repo-template/atom?h=1.1.02018-05-08T17:46:30ZResolve Rubocop warnings2018-05-08T17:46:30ZNate McCurdynate.mccurdy@puppet.com2018-05-08T17:37:30Zurn:sha1:36a278427582e6629141eb8539f658cf1604a528
* Removed the useless assignment in the config_version.rb error catching
* Single quote vs. double quote in Puppetfile
Show the short hostname, not the FQDN in config_version2017-12-15T18:52:14ZNate McCurdynate.mccurdy@puppet.com2017-12-15T18:52:14Zurn:sha1:e5189b5515ea376a7e9763d3ad70e66cf116f24c
This is mainly a style and readability change.
Prior to this, on masters whose hostname is actually their FQDN, the
config_version script would show the entire FQDN. On nodes with really
longs FQDN's, it was not very nice to look at.
This takes the hostname of the master, splits it on dots (.) and takes
the first segment.
Now this: compile-master-02.int.lab.dmz.company-name.net-production-48fd18ab
Is this: compile-master-02-production-48fd18ab
Use the puppet-agent ruby in config_version.rb2017-12-15T18:48:47ZNate McCurdynate.mccurdy@puppet.com2017-12-15T18:48:47Zurn:sha1:09df4b4961da424319d5208740aebbc9009eaa7b
Prior to this, the config_version.rb script (used for r10k) attempted to
use the system ruby to parse the script. This caused problems on Puppet
masters that don't have `ruby` in PATH.
This fixes that by hardcoding the puppet-agent's ruby in the shebang.
config_version: Show the compiling master's name2017-07-06T00:09:51ZNate McCurdynate.mccurdy@puppet.com2017-07-05T23:55:39Zurn:sha1:124b1a2727466e63cf82858bb09749454dae40d3
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
Add ruby shebang to config_version scripts2016-11-22T21:20:15ZNick Walkernick.walker@puppetlabs.com2016-11-19T00:30:28Zurn:sha1:c9931ceef72fb68cbcd981a6922337b3d1719fad
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
Set the execute bit for CM config version script2016-06-29T14:42:23ZReid Vandewielereid@puppetlabs.com2016-06-29T14:38:07Zurn:sha1:d340dd22880d3f16beeb5f2cc1d44b7a125954db
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 to read r10k_deploy.json file2015-12-18T17:24:27ZNick Walkernick.walker@puppetlabs.com2015-12-15T00:28:13Zurn:sha1:56d0908db2919fc9734a7722ece4adaa9d7b9bdc
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
Check for rugged or output UNIX epoch2015-11-20T14:13:17ZRanjit Viswakumarwhatsaranjit@gmail.com2015-11-20T14:12:47Zurn:sha1:c2bd0d3ca1fd4e9f2fce24196201835272fd1e21Checking for git first2015-11-20T14:13:17ZRanjit Viswakumarwhatsaranjit@gmail.com2015-11-20T13:29:17Zurn:sha1:f765903e25e2b7720a3cf52b78700275eb0197d5Update file permsissions to be 755 on scripts2015-08-31T20:20:43ZNick Walkernick.walker@puppetlabs.com2015-08-31T20:20:43Zurn:sha1:869a5c3aa974b53e2f7f4c8fd8ab01fab0420f6d