I haven't yet in this particular run; however, in my puppet ver 2 days, I
created custom facts on the client nodes. I find it hard to believe that was
taken out of mix. A search of puppet docs has this url.
https://docs.puppet.com/facter/3.1/custom_facts.html
I'll probably be trying that one tonight or tomorrow depending on my ability to
troubleshoot what should be a laughably simple class. De-rustifying my PDL
ability is a pain.
If anyone's interested, there are a couple of reasons why I'm having
${::environment} different from $facts['env']. First, when designing their
sdlc process, my company went nuts with different environments - way more than
just the standard dev, qa, uat, prd and those environments won't match the
puppet environments at least while we're rolling it out. Second, I'd like to
be able to get the env from the box when I'm on it. Our naming convention
isn't universal so getting that information is sometimes hit or miss "$ faster
env" will be a lot easier than a MySQL query.
So, short answer and a longer story. Thanks
Doug
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/e16e799e-55cc-416a-b9f8-8e2f2617c826%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
