Add custom communicator to the Hyperv driver
- Dominant language
- Go
- Stars
- 15.8k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
#### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
#### Description
Add the ability to use custom communicators (i.e., shell command line) with specific OSs, such as Talos, that disable SSH.
#### Use Case(s)
Using Talos as an OS which disables SSH.
#### Potential configuration
```
```
#### Potential References
Contributor guide
Research direction
Start by locating the Hyperv driver and its communicator configuration in the Packer repository. Determine how a custom shell command communicator could be selected for operating systems such as Talos, then validate that the configuration supports the stated use case without SSH.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100