cisagov / cisagov/windows-commando-vm-packer
Explore using Ansible to configure the AMI
- Dominant language
- HCL
- Stars
- 11
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
# 💡 Summary #
We should explore using Ansible to configure this, and any Windows, image.
## Motivation and context ##
Currently in #21 all of the logic is being implemented with a series of PowerShell scripts. It might be helpful to handle this image much like our Linux AMIs and use Ansible to configure the image.
## Implementation notes ##
Helpful links:
- [ansible.windows](https://docs.ansible.com/ansible/latest/collections/ansible/windows/index.html#plugins-in-ansible-windows) collection
- [chocolatey.chocolatey.win_chocolatey](https://docs.ansible.com/ansible/latest/collections/chocolatey/chocolatey/win_chocolatey_module.html) module
## Acceptance criteria ##
Explore the viability of switching to using Ansible and implement the switch if possible.
Contributor guide
Research direction
Start by reviewing the PowerShell-based image configuration described in issue #21 and comparing it with the existing Linux AMI approach. Check the ansible.windows collection and chocolatey.chocolatey.win_chocolatey module for Windows support. Done means determining whether Ansible is viable and switching the image configuration if possible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, powershell
- Domain
- devops, infrastructure, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100