Plan for existing DSC 1.1 LCM users to migrate to DSC 3.0 #526
Description
Summary of the new feature / enhancement
So @anmenaga suggested that I raise the questions here that I was asking on the DSC community call last night - here goes!
Currently I have a number of nodes managed with DSC 1.1 using Azure Automation State Configuration - all on-premises Windows Server nodes. The question was really around:
- What benefits should I expect from moving to DSC 1.1 to 3.0 - I understand that newer DSC resources could make this a requirement - but what are the driving forces for someone with this setup, apart from 'staying ahead of the curve'?
- What will moving from DSC 1.1 to DSC 3.0 look like, especially when it comes to the deprecation of the LCM? I currently have a lot of config which is in the 'classic' PowerShell compliation / MOF format - including looping through data stored in .PSD1 files to automate standing up many resources with small differences, and composite resources. Will there be migration tools available, how challenging is the migration expected to be in my scenario.
I'm familiar with the desire to move from MOF to JSON / YAML and why that makes sense, and 'get' how the new model will make it easier for tools Chef, Puppet, Ansible to integrate with DSC. But what's the benefits that those of us using DSC 1.1 in pull mode with the LCM can expect to reap? Just trying to warn about the sense of mere fire and motion.
Proposed technical implementation details (optional)
Making the move DSC 1.1 (including using the LCM) to 3.0 as seamless and pain-free as possible.