You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR feedback: clarify output.json docs and surface missing-status error
- Restructure output.json section: lead with what CAPH reads (status,
message), explain why JSON over plain logs, show minimal examples,
demote extended example to its own subsection
- ParseAndApply now returns error when JSON is invalid or status field
is missing; callers log it at StateFinishedSuccessfully so operators
can see when output.json is present but has no status field
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
When the command finishes (success or failure), CAPH emits a Kubernetes event with reason `ImageURLCommandOutputJSON` containing the full JSON content. If the command failed, the event type is `Warning`; otherwise it is `Normal`. The content is also written to the controller log at key `outputJSON`.
126
-
127
-
When present, CAPH sets the `NodeProvisioningSucceeded` condition on the machine (HCloudMachine or HetznerBareMetalHost) based on the top-level `status` field.
0 commit comments