"As an architect you design for the present, with an awareness of the past for a future which is essentially unknown."
– Herman Foster
– Herman Foster
In the last chapter, we covered what PowerShell DSC is and how it fits into a continuous delivery and DevOps process. DSC uses PowerShell language extensions to define configuration files that express the expected state of a target node. We know that DSC uses DSC resources to determine whether the current state of the target node matches the expected state and that these resources know how to change the current state to the expected state.
In this chapter, we will cover the following topics:
- Push and pull management
- General workflow
- Local configuration manager
- DSC pull server
- Deployment considerations