oxidecomputer / oxidecomputer/oxide.rs

`boot-disk` parameter does not seem to be optional when updating an instance

Open
#1,400 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
75
Forks
21
Avg merge
2d 2h
Merged PRs (30d)
19

Description

According to CLI docs:
"--boot-disk
The disk the instance is configured to boot from. Setting a boot disk is optional but recommended to ensure predictable boot behavior. The boot disk can be set during instance creation or later if the instance is stopped"

However, if we don't define it in our command, we get a failure:

oxide --insecure --timeout 300 --profile oxide24 instance update  --instance fio-instance-mlsc  --ncpu
s 4  --memory 16GiB --project verdant-df --auto-restart-policy never --cpu-platform amd_turin
error: the following required arguments were not provided:
  --boot-disk <boot-disk>

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the instance update CLI argument definition and compare its requiredness with the linked instance/update documentation. Reproduce the shown update command without --boot-disk; done when the documented optional behavior and CLI behavior agree, with a regression check if the project has one.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.