Skip to main content

Desired State Configuration - ConfigurationData

PowershellContact

Update 12.10.2016 - More functions added to repro some while ago

This module has been laying dormant in my BitBucket repro. Looks like people are realizing that DSC is about to become a thing. Need some feedback if this is a way of handling your Configuration data in DSC. I will publish it to the PowershellGallery if people find it useful. Should probably do a code review as well since this was written over 2 years ago :-0.

Update 19.04.2014 - Module (beta) added to bitbucket here

When you start to work with DSC, you quickly realize that separating the infrastructure from the configuration is a huge benefit and somewhat of a curse. You start to read blogs and webposts explaining how you can specify the configurationdata to you configuration, however for the people that does not speak powershell (yes they are out there) and/or still don’t like it, it looks kind of “untidy”. Example:

image

Yes, Beelzebub has joined the party, pure evil. Just to explain ConfigurationData in Desired State Configuration:

It consists of two main elements:
  1. AllNodes (an array of all you nodes you want to configure)
  2. NonNodeData (an hashtable of properties that may or may not be related to any specific node)
So instead of the “rubbish” configdata variable above, we are going to do the same like this:

Import-Module DSCconfigdata

Add-DSCnode -Name Server1
Add-DSCnode -Name Server2

Add-DSCproperty -Name WinFeatures
Add-DSCproperty -Name SourceRoot
Add-DSCproperty -Name WebDirectory
Add-DSCproperty -Name RecurseValue

(Get-DSCNode -Name Server1).Role = "web"
(Get-DSCNode -Name Server1).WinFeatures = "web-server"
(Get-DSCNode -Name Server1).SourceRoot = "\\Server106\source\presentation\"
(Get-DSCNode -Name Server1).WebDirectory = "c:\inetpub\wwwroot\"
(Get-DSCNode -Name Server1).RecurseValue = $false

Add-DSCproperty -NonNodeData -Name DNSIPAddress -Value "8.8.8.8"
Add-DSCproperty -NonNodeData -Name DNSName -Value "resolve.contoso.com"
Add-DSCproperty -NonNodeData -Name SubnetMask -Value "255.255.255.0"
Add-DSCproperty -NonNodeData -Name DNSIPAddress -Value "contoso.com"



Should give you something like this:

image


image

image

The module have these methods:

image

The module also exports a variable called $configData. You may also use the function Get-DSCConfigData, the result is the same. 

One other nice feature is to allow clear text passwords in you MOF-files. Just use the Set-AllowClearTextPassword function to enable this (for all nodes or specific nodes). 

Of course if you just want to inspect the configuration for a node, use this:

image

So the module is still in development, however if you are keen on trying it, hit me up on twitter or post a comment.

Cheers

Comments

Popular posts from this blog

Serialize data with PowerShell

Currently I am working on a big new module. In this module, I need to persist data to disk and reprocess them at some point even if the module/PowerShell session was closed. I needed to serialize objects and save them to disk. It needed to be very efficient to be able to support a high volume of objects. Hence I decided to turn this serializer into a module called HashData.



Other Serializing methods

In PowerShell we have several possibilities to serialize objects. There are two cmdlets you can use which are built in:
Export-CliXmlConvertTo-JSON
Both are excellent options if you do not care about the size of the file. In my case I needed something lean and mean in terms of the size on disk for the serialized object. Lets do some tests to compare the different types:


(Hashdata.Object.ps1)

You might be curious why I do not use the Export-CliXML cmdlet and just use the [System.Management.Automation.PSSerializer]::Serialize static method. The static method will generate the same xml, however we …

Build your local powershell module repository - ProGet

So Windows Powershell Blog released a blog a couple of days ago (link). Not too long after, a discussion emerged about it being to complicated to setup. Even though the required software is open source (nugetgalleryserver), it looks like you need to have Visual Studio Installed to compile it. I looked into doing it without visual stuidio, however I have been unable to come up with a solution. I even tweeted about it since I am not an developer. Maybe someone how is familiar with “msbuild” could do a post on how to do it without VS.

Anyhow one of my twitter-friends (@sstranger) came to the rescue and pointed me in the direction of ProGet, hence the title of this post. ProGet comes in 2 different licensing modes
Free (reduced functionality)Enterprise (paid version with extra features)The good news is that the free version supports hosting a local PowershellGet repository which was my intention anyway. So off we go and create a Configration that can install ProGet for us. This is the conf…

Something completely different – PoshARM

I needed a project for my Xmas holiday and I needed something remotely work related. Thus the dubious PoshARM PowerShell module was born and brought to life during my Xmas holiday. Simply put it is a module that lets you build – for now – simple Azure Resource Manager (ARM) templates with PowerShell . 

The module can also import templates from a file or from the clipboard/string. Your partial template or ready made template can be exported as a PowerShell script. This blog post will walk you through how to use it and the features that is currently implemented. 



Update 08.02.2017:

The module is now published to the PowerShellGallery (https://www.powershellgallery.com/packages/posharm). It is still in beta version, however test coverage have increased and some bugs have been squashed during the testing. Also help is present, however somewhat lacking here and there.

Update 18.01.2017:

The module is now on GitHub. Here is the link to the repro (PoshARM on GitHub)



What is a ARM template?It is a …