Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

📖 Fix a minor typo in API document #1219

Merged
merged 1 commit into from
Feb 17, 2023
Merged

📖 Fix a minor typo in API document #1219

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion docs/api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -574,7 +574,7 @@ It is possible to prevent management of a BareMetalHost object by adding
an annotation `baremetalhost.metal3.io/detached`. This removes the host from
the provisioner, which prevents any management of the physical host (e.g
changing power state, or deprovisioning), but still allows the BMH status
to be updated unlike the `paused` anotation. While in this state the
to be updated unlike the `paused` annotation. While in this state the
OperationalStatus field will be `detached` but the provisioning state will
be unmodified. This API only has any effect for BareMetalHost resources
that are in either `Provisioned`, `ExternallyProvisioned` or `Ready`/`Available`
Expand Down