Add verified config to scenario documentation
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.3k
- Forks
- 304
- PR merge metrics
- No merged PRs in 30d
Description
I have been noticing that certain commands in some scenarios are experiencing different results depending on the source/target operating system selection. For example, I have been attempting the AzSHCI and Kubernetes and AzSHCI Deployment scenarios and experienced different results with the following two OS combinations:
- WS 2019 DC for Scenario.ps1 executing against AzSHCI, version 21H2 cluster node VMs.
- WS 2022 DC for Scenario.ps1 executing against AzSHCI, version 21H2 cluster node VMs.
I haven't had an opportunity to go command-by-command and organize my varying results yet. However, it might be helpful to specify the exact environment that has been verified in the scenario documentation. For example, note in the documentation that you experienced no issues with the code running on a WS 2022 DC against 21H2 nodes.
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
Start with the documentation for the AzSHCI and Kubernetes and AzSHCI Deployment scenarios, then compare the reported WS 2019 DC and WS 2022 DC combinations against AzSHCI 21H2 cluster node VMs. Document the exact environment that has been verified and record any differences found when running Scenario.ps1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100