Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion cli/docs/cli.json
Original file line number Diff line number Diff line change
Expand Up @@ -9173,7 +9173,7 @@
"subcommands": [
{
"name": "recovery-finish",
"about": "Clear system recovery status\n\nInstructs the system that a system recovery operation (\"mupdate\") was completed using the software in the specified release.\n\nThe system recovery operation is used to bypass the control plane to deploy known-working software when the control plane itself is not functioning or otherwise unable to update itself. When the control plane detects this, it stops making any changes to deployed software to avoid reverting the recovery itself. This operation puts the control plane back in charge of determining what software should be deployed, instructing it that the specified software (which is also what's currently running) is what's supposed to be deployed.\n\nIf the provided version does not match what's currently running, the control plane will continue to avoid changing deployed software until this operation is invoked with the correct version.\n\nThis endpoint should only be called at the direction of Oxide support.",
"about": "Clear system recovery status\n\nInstructs the system that a system recovery operation (\"mupdate\") was completed using the software in the specified release.\n\nThe system recovery operation is used to bypass the control plane to deploy known-working software when the control plane itself is not functioning or otherwise unable to update itself. When the control plane detects this, it stops making any changes to deployed software to avoid reverting the recovery itself. This operation puts the control plane back in charge of determining what software should be deployed, instructing it that the specified software (which is also what's currently running) is what's supposed to be deployed.\n\nIf the control plane knows the version of all running software (e.g., a single sled was recovered to the same version as the rest of the rack), requests where the provided version does not match what's currently running will fail. If the control plane does not know the version of all running software (e.g., the entire rack was mupdated to a new release), requests with an incorrect provided version will succeed, but the control plane will continue to avoid changing deployed software until this operation is invoked with the correct version.\n\nThis endpoint should only be called at the direction of Oxide support.",
"operation_id": "system_update_recovery_finish",
"args": [
{
Expand Down
13 changes: 9 additions & 4 deletions cli/src/generated_cli.rs
Original file line number Diff line number Diff line change
Expand Up @@ -8361,10 +8361,15 @@ impl<T: CliConfig> Cli<T> {
itself. This operation puts the control plane back in charge of determining \
what software should be deployed, instructing it that the specified software \
(which is also what's currently running) is what's supposed to be \
deployed.\n\nIf the provided version does not match what's currently running, \
the control plane will continue to avoid changing deployed software until this \
operation is invoked with the correct version.\n\nThis endpoint should only be \
called at the direction of Oxide support.",
deployed.\n\nIf the control plane knows the version of all running software \
(e.g., a single sled was recovered to the same version as the rest of the rack), \
requests where the provided version does not match what's currently running will \
fail. If the control plane does not know the version of all running software \
(e.g., the entire rack was mupdated to a new release), requests with an \
incorrect provided version will succeed, but the control plane will continue to \
avoid changing deployed software until this operation is invoked with the \
correct version.\n\nThis endpoint should only be called at the direction of \
Oxide support.",
)
}

Expand Down
2 changes: 1 addition & 1 deletion cli/tests/data/docs-text.txt
Original file line number Diff line number Diff line change
Expand Up @@ -415,7 +415,7 @@ Instructs the system that a system recovery operation ("mupdate") was completed

The system recovery operation is used to bypass the control plane to deploy known-working software when the control plane itself is not functioning or otherwise unable to update itself. When the control plane detects this, it stops making any changes to deployed software to avoid reverting the recovery itself. This operation puts the control plane back in charge of determining what software should be deployed, instructing it that the specified software (which is also what's currently running) is what's supposed to be deployed.

If the provided version does not match what's currently running, the control plane will continue to avoid changing deployed software until this operation is invoked with the correct version.
If the control plane knows the version of all running software (e.g., a single sled was recovered to the same version as the rest of the rack), requests where the provided version does not match what's currently running will fail. If the control plane does not know the version of all running software (e.g., the entire rack was mupdated to a new release), requests with an incorrect provided version will succeed, but the control plane will continue to avoid changing deployed software until this operation is invoked with the correct version.

This endpoint should only be called at the direction of Oxide support.
oxide system update repo list — List all TUF repositories
Expand Down
4 changes: 2 additions & 2 deletions oxide.json
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
"url": "https://oxide.computer",
"email": "api@oxide.computer"
},
"version": "2026072800.0.0"
"version": "2026073100.0.0"
},
"paths": {
"/device/auth": {
Expand Down Expand Up @@ -12939,7 +12939,7 @@
"system/update"
],
"summary": "Clear system recovery status",
"description": "Instructs the system that a system recovery operation (\"mupdate\") was completed using the software in the specified release.\n\nThe system recovery operation is used to bypass the control plane to deploy known-working software when the control plane itself is not functioning or otherwise unable to update itself. When the control plane detects this, it stops making any changes to deployed software to avoid reverting the recovery itself. This operation puts the control plane back in charge of determining what software should be deployed, instructing it that the specified software (which is also what's currently running) is what's supposed to be deployed.\n\nIf the provided version does not match what's currently running, the control plane will continue to avoid changing deployed software until this operation is invoked with the correct version.\n\nThis endpoint should only be called at the direction of Oxide support.",
"description": "Instructs the system that a system recovery operation (\"mupdate\") was completed using the software in the specified release.\n\nThe system recovery operation is used to bypass the control plane to deploy known-working software when the control plane itself is not functioning or otherwise unable to update itself. When the control plane detects this, it stops making any changes to deployed software to avoid reverting the recovery itself. This operation puts the control plane back in charge of determining what software should be deployed, instructing it that the specified software (which is also what's currently running) is what's supposed to be deployed.\n\nIf the control plane knows the version of all running software (e.g., a single sled was recovered to the same version as the rest of the rack), requests where the provided version does not match what's currently running will fail. If the control plane does not know the version of all running software (e.g., the entire rack was mupdated to a new release), requests with an incorrect provided version will succeed, but the control plane will continue to avoid changing deployed software until this operation is invoked with the correct version.\n\nThis endpoint should only be called at the direction of Oxide support.",
"operationId": "system_update_recovery_finish",
"requestBody": {
"content": {
Expand Down
11 changes: 8 additions & 3 deletions sdk/src/generated_sdk.rs
Original file line number Diff line number Diff line change
Expand Up @@ -66783,7 +66783,7 @@ pub mod types {
///
/// API for interacting with the Oxide control plane
///
/// Version: 2026072800.0.0
/// Version: 2026073100.0.0
pub struct Client {
pub(crate) baseurl: String,
pub(crate) client: reqwest::Client,
Expand Down Expand Up @@ -66824,7 +66824,7 @@ impl Client {

impl ClientInfo<()> for Client {
fn api_version() -> &'static str {
"2026072800.0.0"
"2026073100.0.0"
}

fn baseurl(&self) -> &str {
Expand Down Expand Up @@ -72696,7 +72696,12 @@ pub trait ClientSystemUpdateExt {
/// instructing it that the specified software (which is also what's
/// currently running) is what's supposed to be deployed.
///
/// If the provided version does not match what's currently running, the
/// If the control plane knows the version of all running software (e.g., a
/// single sled was recovered to the same version as the rest of the rack),
/// requests where the provided version does not match what's currently
/// running will fail. If the control plane does not know the version of all
/// running software (e.g., the entire rack was mupdated to a new release),
/// requests with an incorrect provided version will succeed, but the
/// control plane will continue to avoid changing deployed software until
/// this operation is invoked with the correct version.
///
Expand Down
Loading