I have been working on setting up a build&test pipeline for a configuration of 5 server roles (app, web, database, etc.).
The pipeline runs in TFS. There is a build agent on a VM in azure in the same virtual network where the VMs are provisioned. The build agent server is also running a tug server. I also have a domain controller and certificate authority as ‘persistent’ vms to ease the process of remoting to the configured vms (no need to configure trustedhosts etc.)
- build and publish config to tug server in azure.
- provision vms in azure, and join them to the domain.
- apply LCM configuration with configuration names to the provisioned vms
- update-dscconfiguration on the provisioned vms
- execute pester test suite to confirm configuration is correct
- delete azure resource group where the vms were provisioned
The problem is the VMs seem to be immediately applying the configuration after the LCM is configured. I would like to be able to apply the configuration through update-dscconfiguration -verbose -wait -ComputerName $ComputerName so that I can see the result of applying the configuration in the build output. Is there a way to prevent the LCM from automatically pulling and applying configurations when configured?