Technical Debt February, Part 2
Windows
WinRM bootstraps are once again working. WinRM certificate authentication ceased working on recent official Microsoft base images at some point. Our workaround for now is to use password authentication over SSL.
Ansible now works correctly as a Groomer for Windows nodes, as does password retrieval for Windows hosts on Google Cloud.
Mu-flavored AWS base images are now available for the platforms win2k12, win2k16, and win2k19. Setting windows as the target platform will resolve to win2k16.
Quality-of-Life Improvements
- Massive refactoring in AWS resource implementations for improved maintainability.
MU::Config: Cough up a filename and line number when someone references a bad ERB variable, or on ERB problems generally- Improved test coverage
Known Issues
- Azure Windows VMs hang indefinitely, even using the official release images.
- GCP password retrieval for Windows nodes does not work consistently on 2016 or 2019
- NTLM passwords over unverified SSL, which we are currently forced to use for all WinRM connectivity, is barely secure. We have open backlog issues for figuring out why certificate auth ceased working, and why verification against our internal CA doesn't behave as expected.