darkoperator / darkoperator/Posh-SSH
Trusted Host Keys - Storing multiple keys per host
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.1k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
looking to have the ability to have multiple entries for a single host.
I am a sys admin for some applications that are on clusters, with the application moving to 1 of multiple nodes. There is a VIP address to target the active node, and I prefer to jump directly to the node that is active for the application.
I can look to see if this is an easy update, and submit a PR for it. But I would like to hear of any issues or concerns before pursuing it.
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
No files, tests, or entry points are named in the issue. First clarify how multiple trusted keys should be represented and selected for one host, then define the expected clustered-host behavior and coverage needed to confirm it.
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
- 35/100