Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

New Puppet Release Supports Running Agents in Windows

DZone's Guide to

New Puppet Release Supports Running Agents in Windows

· DevOps Zone ·
Free Resource

The need for DevOps innovation has never been greater. Get the results from over 100 business value assessments in this whitepaper, Digital Darwinism: Driving Digital Transformation, to see the positive impact of DevOps first hand.

Good news for Puppet users!  The recent 2.7.6 update now gives you support for running puppet agents in Windows for some important resource types.  Specifically these ones:

  • file
  • user
  • group
  • scheduled_task (new type; not cron)
  • package (MSI)
  • service
  • exec
  • host

Support has also been added for running puppet agent and communicating with a remote puppet master.  You can also now apply manifests locally with puppet apply.  Currently, Puppet does not support running a puppet master on Windows, and the engineers currently have no plans to add that support.

In other news, there was also an important security warning today for puppet users:

We have discovered a security vulnerability (“AltNames Vulnerability”) whereby a malicious attacker can impersonate the Puppet master using credentials from a Puppet agent node. This vulnerability cannot cross Puppet deployments, but it can allow an attacker with elevated privileges on one Puppet-managed node to gain control of any other Puppet-managed node within the same infrastructure.

All Puppet Enterprise deployments are vulnerable, and Puppet open source deployments may be, depending upon their site configuration.
-- Puppet Labs

Stay vigilant!

Interested in Kubernetes but unsure where to start? Check out this whitepaper, A Roundup of Managed Kubernetes Platforms from Codeship by Cloudbees, for an overview and comparison of Kubernetes platforms. 

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}