Mark

Thinking of something like this: 

I've got a draft created, but wondering if there's real benefit to maintain it. As there's an element of duplication between Bash and PowerShell. I've created a feature branch (mwg-powershell-helper)...

@Gordonby Would this be acceptable, as it includes a cli and bash script? 

That postdeploy.sh script will be the challenge. To move this one forward we'd need to rewrite it to run in PowerShell. I'll start to think about a solution here. Not...

There's also an option to use the api to get the list of sku's in a region. https://management.azure.com/subscriptions/{{subscriptionId}}/providers/Microsoft.Batch/locations/ukwest/virtualMachineSkus?$filter=&api-version=2022-06-01 Then filter the list on "EphemeralOSDiskSupported". Wonder if this would work?

FYI, @Gordonby Added a change to load the VM Sku's from a json file. Place added a property "location" which to filter by location from screen and also have a...

I did start rewriting the bash script in PowerShell and got it to 90% ready, but again created tech. debt with the need to maintain 2 versions of the post...

I've started on the PowerShell script again to complete the last bits and pieces. Did loose a weeks work by forgetting to push a change :( My bad!

Made a small change in approach for this one. Now only converting thee bash postdeploy file to PowerShell and leaving the rest to use az cli. Feels like a good...