PowerShell / PowerShell/Win32-OpenSSH
Ensure that chosen installation framework is automation ready
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
I have been doing the chocolatey package and just wanted to express a requirement that if an installer is eventually created by this project that it should be automation ready.
This would seem to include as least:
- choosing a framework that has command line automation capabilities.
- ensuring that common customization requirements are instrumented to be exposed on the command line (e.g. if "generate server keys" is an option in the interactive installer, then there should be an install parameter that exposes it as well. Same with an option on whether or not to install the sshd server)
- documenting installation automation parameters.
In addition to just being a best practice, this would allow me to conform the current features supported in the chocolatey package to use the formal installer immediately upon release.
Contributor guide
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
The issue names no files, tests, or installer entry point. Start by locating the planned installer and the existing Chocolatey package, then determine how automation parameters and customization options should be exposed and documented; done means unattended installation supports those options and the parameters are documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, documentation, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100