redhat-developer / redhat-developer/mapt
[Azure] Add network security group rules to allow traffic for WINRM ports
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
For being able to use ansible to configure a provisioned windows machine it is necessary to have communication via winrm, which is not currently part of the network security groups created by mapt
I think we should make this configurable using a flag to the mapt azure windows create command instead of having it enabled by default for all provisioned windows machines
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the implementation of the mapt azure windows create command and trace where its network security groups are created. Add a configurable option for WinRM traffic, keeping the default behavior unchanged; done means the requested rules appear only when enabled and the command remains usable without the option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, azure, go
- Domain
- cli, cloud, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100