You can adjust the config_version value in puppet.conf (
https://docs.puppet.com/puppet/latest/configuration.html#configversion) to
spit out the git hash. See "Per-environment config_version" at
http://garylarizza.com/blog/2014/08/31/r10k-plus-directory-environments/
for some detail on it and an ex
I am sorry i do not quite catch your meaning Rob.
Could you please explain?
Thank you
On Tuesday, February 28, 2017 at 9:26:01 PM UTC-6, Rob Nelson wrote:
>
> If you're using a control repo, you can change the catalog version number
> from seconds since epoch to git commit hash, which should all
If you're using a control repo, you can change the catalog version number
from seconds since epoch to git commit hash, which should allow you to
reconstitute all the modules in use at that time if you pin all external
modules in your Puppetfile (included would already be part of that hash).
--
Rob
This is an excellent question Jason, I don't know the answer myself, but it
looks like I just submitted a similar question.
--
Warron French
On Tue, Feb 28, 2017 at 3:30 PM, Jason McMahan
wrote:
> Good day,
> I was wondering if others could offer their thoughts, advice
Good day,
I was wondering if others could offer their thoughts, advice?
We would like to tag any new servers built with a build version, and tie
that build version to all modules that were used for building it?
For instance if i built server test1 and it was tagged with
build.2_28_2017_1.0 we c
