control-repo-template/scripts, branch config_version_lirionpuppetlabs/control-repo extended with not-so-core stuffhttps://git.pfeiffer.tech/control-repo-template/atom?h=config_version_lirion2025-08-15T05:21:01Z+ config_version implementations with commit message2025-08-15T05:21:01ZHarald Pfeifferpuppet@lirion.de2025-08-15T05:21:01Zurn:sha1:d2221daeb81ad9f627d2499fa7817ea1cf3379c5check if git repo exists when generating config version2022-07-16T17:59:00ZMiles Stötznermiles@stoetzner.de2022-07-16T17:59:00Zurn:sha1:ffc8ef90aea3512afacd02c3c2ce939f35d56d7aDon't assume git is in /usr/bin; expect it on PATH2019-10-16T20:05:33ZReid Vandewielereid@puppet.com2019-10-16T19:46:30Zurn:sha1:e46d209f19ad94c89652bec8064a8b6ce880a752Restore and clarify config_version functionality2019-10-16T17:26:21ZReid Vandewielereid@puppet.com2019-10-16T17:16:34Zurn:sha1:ada94157a42e1d20112eaa74618e2f22db4ed560
This branch is intended as a portability fix. Some functionailty had
been inadvertently removed as unused, but testing revealed that it had a
purpose. Because the purpose was unclear, this commit restores the
functionality AND clarifies it in the script names and comments in
config_version.sh.
Remove code dead for more than 2 years2018-05-11T20:28:40ZRomain Tartièreromain@blogreen.org2018-04-07T09:59:18Zurn:sha1:415a71dd59c17093684efd3a1376afe1bfb8824d
r10k generates a .r10k-deploy.json file since version 2.1.0 which was
released on October 28, 2015. New users of the control-repo are not
likely to have a so old version of r10k, so remove this dead code.
Do sanity checking early2018-05-11T20:26:49ZRomain Tartièreromain@blogreen.org2018-04-07T09:34:07Zurn:sha1:211ecc58b5b650ed158f0c36158a85a289ce2640
Fail before doing anything when passed parameters are invalid.
Remove execute permission and shebangs2018-05-11T20:26:49ZRomain Tartièreromain@blogreen.org2018-04-07T09:18:26Zurn:sha1:61d0147e494521aff0c4d80abda52abde774c27e
The appropriate ruby interpreter is determined by the config_version.sh
shell script which explicitely use it to start these ruby scripts.
Removing the execute bit ensure users will not run these script with the
wrong Ruby version.
Improve portability2018-05-11T20:25:27ZRomain Tartièreromain@blogreen.org2018-04-07T09:13:41Zurn:sha1:ffc1769d2e9ab6057d44660e2ef4430a70652836
- Fix shebang: `bash` is not always in `/bin/`, and since the script
does not have bashism, rely on `sh` which is always in `/bin/`;
- Use `/opt/puppetlabs/puppet/bin/ruby` if this file exist and is
executable, otherwise use `ruby` from $PATH;
- Use `code_manager_config_version.rb` if `.r10k-deploy.json` is found,
and `config_version.rb` in all other cases.
Resolve 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