I have use the Windows DSC module to add a window 2016 server to a domain.
dsc_xcomputer { 'domain_membership':
dsc_name => $facts['hostname'],
dsc_domainname => $domain_name,
dsc_credential => {
'user' => "${username}@${domain_name}",
'password' =>
Same issue:
May 21 11:26:51 vm01 puppet-agent[419]: Shutdown/restart in progress
(:restart_requested); skipping run
May 21 12:26:51 vm01 puppet-agent[419]: Shutdown/restart in progress
(:restart_requested); skipping run
May 21 13:26:51 vm01 puppet-agent[419]: Shutdown/restart in progress
All ,
Greetings !,
I am facing a problem with my legacy community version puppetmaster 3.7
,Which stops in between .I was trying to enable the logs ,but the methods
mentioned in the documentation ( adding log_level =debug in puppet.conf )
seems not applicable in this version .In my case
Using include instead of class makes sense to me and was my instinctive
thought.
Why on earth, then, do all the (or most) of the Puppet Forge modules use
the
class{'myclass':
param1 => 'thing'
}
patterns in their examples. I had begun to believe that was the preferred
pattern.
I will mend
Most likely because that’s an easy way to show the parameters a class
supports. Some modules use hiera data to show that, though it is a bit more
complicated to explain and understand, especially for novices.
On Tue, May 21, 2019 at 9:42 AM Peter Berghold
wrote:
> Using include instead of class
Hi there,
I am new to puppet.
I want to know how to start puppet master for v6.0.0 or late versions.
For version below v6.0.0, I can install puppet by:
gem install puppet -v 5.5.14
Then start by :
puppet master --verbose --no-daemonizepuppet
However, after v6.0.0, there is
