<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Featured on James Pogran</title><link>https://pogran.dev/tags/featured/</link><description>Recent content in Featured on James Pogran</description><generator>Hugo</generator><language>en</language><copyright>Copyright © 2008–2025, James Pogran</copyright><lastBuildDate>Thu, 19 Oct 2017 14:13:06 -0400</lastBuildDate><atom:link href="https://pogran.dev/tags/featured/index.xml" rel="self" type="application/rss+xml"/><item><title>Diagnosing DSC and Puppet Executions</title><link>https://pogran.dev/diagnosing-dsc-and-puppet-executions/</link><pubDate>Thu, 19 Oct 2017 14:13:06 -0400</pubDate><guid>https://pogran.dev/diagnosing-dsc-and-puppet-executions/</guid><description>&lt;p&gt;While developing your Puppet manifests using the Puppet DSC module you might run into a problem with one of the DSC Resources.&lt;/p&gt;
&lt;p&gt;The problem shows itself every execution, when Puppet says that the state has drifted and needs to be corrected. When you look at the state of the target node it appears to be correct, something must be wrong with Puppet, right? Well, as with most things, the answer is more complicated than it appears.&lt;/p&gt;</description></item></channel></rss>