[FEATURE REQUEST] Update `amigen9-build.sh` to properly function in Azure
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 105
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
When attempting to use the azure-chroot builder (actually, a modified version thereof), the current logic for computing the installation-target fails. Need to update so that it functions, correctly.
- Logic needs to properly-compute the target disk, whether or not the (chroot) builder-host has a waagent-managed (ephemeral) disk attached
- Logic needs to properly-compute the target disk, whether or not the (chroot) builder-host is using standard/legacy SCSI devices or using NVMe devices
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 amigen9-build.sh and trace the logic that computes the installation target. Exercise it with and without a waagent-managed ephemeral disk, and with both standard or legacy SCSI and NVMe devices. Done means the target disk is computed correctly for all four Azure builder-host combinations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, shell
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100