I'm trying to sort out CI builds using TFS/VSTS that use packer and other tools.
Currently I use packer validate to prove that its working ok, but there appeared to be no way of validating the answer files for windows other than loading them into the AIK.
I found a blog post here http://schneegans.de/computer/unattend-schema/ which suggested how to get at the schema, so I set about knocking some powershell functions together to extract the schema programatically (I'm not posting the schema as I dont want to start having to read too many licence agreements) and then use this to validate the XML against what is in the schema.
I appreciate there is a fair bit of refactoring that could be done and no pester tests - but I've cobbled / pasted these together in this format for the purposes of the internet and removed logic that is only appropriate for my environment.
Not saying they will be perfect or usuable in every locale.. Works on my machine though.
script is located here https://gist.github.com/davidwallis3101/48454cb6c17c988de43b5ea17089ea6f
.:. David Wallis .:.
I try to specialise in doing the out of the ordinary stuff (A Challenge!) - And generally making life as easy as possible using any of the technologies within reach without having to re-invent the wheel where possible! Technologies and products can include -> .NET, VBS, Powershell, DSC, Systems Center, NetApp, VMWare, Windows Server, Linux, Python, Microcontrollers and others!
Thursday 9 May 2019
Tuesday 2 April 2019
Refactoring PSM1 based modules into seperate ps1 files
A lot of my old powershell modules have grown to be quite big and unweildly.
At work we have now standardised on using PSAKE to create them and use a structure that has a public and private set of folders that contain ps1 files that make up the modules functions. These are automatically dot sourced when the module loads.
I'm not going to claim credit for doing it that way, its based on some complex googling, or maybe just plain luck.
In an effort to refactor and make some of these more readable, supportable, easier to test using pester etc etc.. I've knocked up a quick and dirty script for 'refactoring' the module into seperate files.
It's not perfect but it was spend a little time writing a script to do it, rather than spending the time manually in VSCode or Notepad++
The code uses powershell's Abstract Syntaxt Tree / Language Parser. it might help someone, it might not :)
Code is here: https://gist.github.com/davidwallis3101/58de8462bf37c8683b377cb0c7a5a95b
At work we have now standardised on using PSAKE to create them and use a structure that has a public and private set of folders that contain ps1 files that make up the modules functions. These are automatically dot sourced when the module loads.
I'm not going to claim credit for doing it that way, its based on some complex googling, or maybe just plain luck.
In an effort to refactor and make some of these more readable, supportable, easier to test using pester etc etc.. I've knocked up a quick and dirty script for 'refactoring' the module into seperate files.
It's not perfect but it was spend a little time writing a script to do it, rather than spending the time manually in VSCode or Notepad++
The code uses powershell's Abstract Syntaxt Tree / Language Parser. it might help someone, it might not :)
Code is here: https://gist.github.com/davidwallis3101/58de8462bf37c8683b377cb0c7a5a95b
Thursday 22 June 2017
Creating a pester script with powershell
I’m knocking up a few more infrastructure validation tests and couldn’t be bothered to write everything, so with the quick script it gets you a starting point, creating a simple test for each value that ends with ver (version).
Obviously this needs further work, but not a bad starting point.
$results = Get-ItemProperty -Path "HKLM:\Software\Wow6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\Misc."
foreach ($property in $results.PSObject.Properties) {
if ($property.Name -like '*Ver') {
write-host "It `"$($property.Name) has a valid version`" {"
Write-Host " `$results.$($property.Name) | Should Be `"$($property.Value)`""
Write-Host "}"
Write-Host
}
}
Friday 18 November 2016
Getting nested runbooks in system center orchestrator
I have recently written a function for checking if a runbook is checked out (will post that shortly) but I wanted a way of checking if any child runbooks were checked out too..
I did a google and found a link on ServerFault for a sql query that did just that (I've lost the link), I've taken that SQL query and wrapped it in a Powershell step so that I can use it easily on my desktop inside or outside of orchestrator - Outside of orchestrator will be to be used in my pester tests which I use to verify runbooks, but also the whole end to end process, IE are all required runbooks checked in?
The script is as follows:
I did a google and found a link on ServerFault for a sql query that did just that (I've lost the link), I've taken that SQL query and wrapped it in a Powershell step so that I can use it easily on my desktop inside or outside of orchestrator - Outside of orchestrator will be to be used in my pester tests which I use to verify runbooks, but also the whole end to end process, IE are all required runbooks checked in?
The script is as follows:
function Get-ChildRunbooks { <# .SYNOPSIS Get-ChildRunbooks .DESCRIPTION Gets the runbooks that are called by a parent runbook, you will need permissions to query the sql database Requires PS V3 .PARAMETER RunbookName The runbook name to check .PARAMETER Database The database name to connect to .PARAMETER Server The name of the server hosting orchestrators SQL instance .PARAMETER Recurse Switch for enabling recursion .EXAMPLE PS C:\> Get-ChildRunbooks -Name 'VMWare' .EXAMPLE PS C:\> Get-ChildRunbooks -Name 'VMWare' -Recurse .EXAMPLE PS C:\> Get-ChildRunbooks -Name 'VMWare' -Database Orchestrator2012 .EXAMPLE PS C:\> Get-ChildRunbooks -Name 'VMWare' -Database Orchestrator2012 -Server Orchestrator001 .LINK http://blog.wallis2000.co.uk #> [CmdletBinding()] [OutputType([System.Int32])] param( [Parameter(Position=0, Mandatory=$true)] [alias("Name")] [ValidateNotNullOrEmpty()] [System.String] $RunbookName, [Parameter(Position=1)] [System.String] $Database = 'Orchestrator', [Parameter(Position=2)] [System.String] $Server = 'myserver', [Switch]$Recurse ) try { $Results = @() $Query = @" SELECT POLICIES.Name AS [SourceRunbook], TRIGGER_POLICY.PolicyPath, RIGHT(TRIGGER_POLICY.PolicyPath, CHARINDEX('\', REVERSE(TRIGGER_POLICY.PolicyPath))-1) as ShortPolicyPath FROM OBJECTS INNER JOIN POLICIES ON OBJECTS.ParentID = POLICIES.UniqueID INNER JOIN TRIGGER_POLICY ON OBJECTS.UniqueID = TRIGGER_POLICY.UniqueID WHERE (OBJECTS.Deleted = 0) AND (OBJECTS.ObjectType = '9C1BF9B4-515A-4FD2-A753-87D235D8BA1F') AND (POLICIES.Name = '$RunbookName') "@ $connectionString = "Server=$Server; Database=$Database;Trusted_Connection=Yes; Integrated Security=SSPI;" #connect to database $connection = New-Object System.Data.SqlClient.SqlConnection($connectionString) $connection.Open() $command = $connection.CreateCommand() $command.CommandText = $Query $command.CommandTimeout = 30 $adapter = New-Object System.Data.SqlClient.SqlDataAdapter $command $dataset = New-Object System.Data.DataSet $adapter.Fill($dataset) | out-null foreach ($Row in $dataset.Tables[0].Rows) { $Results+=[pscustomobject][ordered]@{ SourceRunbook= $Row.SourceRunbook; PolicyPath=$Row.PolicyPath;` ShortPolicyPath=$Row.ShortPolicyPath} if ($Recurse) { $results+= Get-ChildRunbooks -Name $Row.ShortPolicyPath -Recurse } } $connection.Close() return $results } catch { throw } }
Thursday 23 July 2015
Getting all automation connections from within SMA of a given type
I'm currently looking at how I can migrate some runbooks from System Center Orchestrator 2008 R2 to Service Management Automation (SMA). One issue I have in Orchestrator is that it isn't possible to subscribe to a configuration activity if you package it up into an Orchestrator Integration pack (OIP). To get around this, you can use the invoke.net activity and call the Class directly from the DLL.
Why does it matter your thinking? One scenario we have is that we want to be able to have a common runbook, and execute it against multiple load balancers. Each of these connections is then stored in Orchestrator.. and the caller passes the configuration name in (which is actually the lb hostname) and then it connects with the correct credentials.
Anyway I was thinking about how I could do the same or achieve the same in SMA, and realised that it was a non issue, I then started migrating some other runbooks, and one task requires running against all instances of an env.. for example VMWare - Go get all VM's across all vcenters..
I thought I'll just get all the connections of a given type and easy done, however Get-AutomationConnection has a mandatory parameter of the name.. and wildcards don't work.
I had a quick nosy in the database and realised it should be easy to do what I needed, so what I have done is create a workflow that queries the relevant table in the DB for the connections and then returns the name so you can use that to return the credential / connection pair required. This maybe achievable in other ways but I am new to SMA :)
The scripts are available here: Get-AutomationConnections.ps1 and an example of calling it here: UseMultipleConnections.ps1
Why does it matter your thinking? One scenario we have is that we want to be able to have a common runbook, and execute it against multiple load balancers. Each of these connections is then stored in Orchestrator.. and the caller passes the configuration name in (which is actually the lb hostname) and then it connects with the correct credentials.
Anyway I was thinking about how I could do the same or achieve the same in SMA, and realised that it was a non issue, I then started migrating some other runbooks, and one task requires running against all instances of an env.. for example VMWare - Go get all VM's across all vcenters..
I thought I'll just get all the connections of a given type and easy done, however Get-AutomationConnection has a mandatory parameter of the name.. and wildcards don't work.
I had a quick nosy in the database and realised it should be easy to do what I needed, so what I have done is create a workflow that queries the relevant table in the DB for the connections and then returns the name so you can use that to return the credential / connection pair required. This maybe achievable in other ways but I am new to SMA :)
The scripts are available here: Get-AutomationConnections.ps1 and an example of calling it here: UseMultipleConnections.ps1
Wednesday 8 July 2015
Executing SMA runbooks from linux
I've been trying to work out a way of executing SMA runbooks from some of our linux systems.
so I have knocked together a crude python script that can be further extended for doing such a task..
python isn't my language of choice - this is probably quite apparent in the lack of classes etc.
typically SMA uses ODATA for the interface via REST - this was proving too much of an issue, so I resorted to regex and extracting the data from the XML that I needed.. Initially I was going to use XPATH to do it, but things like elementtree didn't seem to like the 'XML'.
Below is a pic of the output:
Anyway I have uploaded the script to my codeplex site located here: http://smaworkflows.codeplex.com/SourceControl/latest#Python/SMARunbooks.py
Also a thanks should be mentioned to Laurie Rhodes for the information provided here:
http://www.laurierhodes.info/?q=node/105
so I have knocked together a crude python script that can be further extended for doing such a task..
python isn't my language of choice - this is probably quite apparent in the lack of classes etc.
typically SMA uses ODATA for the interface via REST - this was proving too much of an issue, so I resorted to regex and extracting the data from the XML that I needed.. Initially I was going to use XPATH to do it, but things like elementtree didn't seem to like the 'XML'.
Below is a pic of the output:
Anyway I have uploaded the script to my codeplex site located here: http://smaworkflows.codeplex.com/SourceControl/latest#Python/SMARunbooks.py
Also a thanks should be mentioned to Laurie Rhodes for the information provided here:
http://www.laurierhodes.info/?q=node/105
Saturday 4 July 2015
SMA Workflows
I'm trying to get to grips with SMA and what it will take for us to migrate existing integration packs and runbooks that we have authored in C#
I'm going to try and keep everything we have done open, So I am uploading all the scripts to a new codeplex site I created located here: smaworkflows.codeplex.com
I've just created one for sending text messages via a provider called AQL for more details see here: www.aql.com/sms/
The above script is located here: http://smaworkflows.codeplex.com/SourceControl/latest#Misc/Send-SMS.ps1 if anyone is interested.
I'm going to try and keep everything we have done open, So I am uploading all the scripts to a new codeplex site I created located here: smaworkflows.codeplex.com
I've just created one for sending text messages via a provider called AQL for more details see here: www.aql.com/sms/
The above script is located here: http://smaworkflows.codeplex.com/SourceControl/latest#Misc/Send-SMS.ps1 if anyone is interested.
Subscribe to:
Posts (Atom)