darkoperator / darkoperator/Posh-SSH
A feature request not a bug- implement Invoke-SSHStreamExpect without the Action part
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.1k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
I think that this is more in keeping with the way that Expect is usually used. In other words, issue the first command and wait for either the expected response or a timeout. Return either the response or an error. Not sure of the proper response, maybe just normal or error with the ability to then read back the response text buffer.
Then, instead of just blindly throwing the Action at the stream, another Invoke-SSHStreamExpect could be done for the next command.
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 by reviewing the existing Invoke-SSHStreamExpect entry point and how it currently handles the command, expected response, timeout, and Action. Define the response or error behavior and how response text remains readable for a later invocation. Done means separate invocations can issue and await commands without requiring an Action, but no files or tests are identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100