Repository navigation
📖 docs: explain how to edit hive.yaml - #19188
Conversation
Locate the persisted YAML by deployment, explain dashboard exports and Settings coverage, and show how to validate and apply manual changes. Hive-Run: hivecommons#19187 Hive-Plan: Editing hive.yaml operator guide Hive-Spec: hivecommons#19187 Co-authored-by: Nate W <4453979+nate-double-u@users.noreply.github.com> Signed-off-by: Karibhou <157208370+Karibhou@users.noreply.github.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Open PR overlap checkBase branch: Conflicts are checked with every PR merged onto the current tip of
|
There was a problem hiding this comment.
Intent-alignment: the PR covers the four gaps in #19187 (location per deployment, hosted/no-shell guidance incl. review.analysis_factcheck as YAML-only, reload vs restart, layers/export/download) and links the guide from techdocs-assessment.md, as the issue asked. I checked the new relative links and the #configuration-blocks, #config-export-is-not-a-backup and fact-check anchors at the merge base; they resolve. Docs only; no scope creep.
Advisory (non-blocking):
src/docs/settings.md:7- the existing pointer toconfig-layering.md("which file a saved setting is written to") was replaced rather than supplemented. The new guide links to it, so it is still reachable, but the Settings page no longer answers that question directly. Consider keeping both links.src/docs/editing-hive-yaml.md- issue item 2 asked for a list of keys Settings covers; the guide gives examples plus the parity allowlist and says it is not an exact list. That is an honest answer, but it is a partial one.
-- hive: agent=adjudicator-3 backend=claude model=claude-sonnet-5-5 claude=2.1.327
|
Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor. Review follow-ups: 1 open of 1 (below
|
|
This closes most of #19187. Two contradictions remain in pages the PR doesn't touch, and What it fixes
Fix in this PR or a follow-up
Suggestions (non-blocking)
I read the diff against the published docs only. I did not verify paths, Review drafted by Claude (Anthropic) and edited by @nate-double-u. Checked against the diff and published docs only, not against code behavior. |
|
/lgtm Posted by @clubanderson from the Hive dashboard; the merge gate decides from here. |
|
@hivecommons-hive[bot]: changing LGTM is restricted to collaborators DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/approve Posted by @clubanderson from the Hive dashboard; the merge gate decides from here. |
There was a problem hiding this comment.
Approved by @clubanderson for Hive auto-merge on green CI.
Approved from the Hive dashboard by @clubanderson as the owner decision on a Ready-for-human-merge pull request; hive merges it on its next merge pass once CI is green.
Fixes #19187
What changed
hive.yamlon Kubernetes, Podman, Docker Compose, and native macOS/Linux.review.analysis_factcheckneeds a deployment operator.Verification
Docs only; no runtime tests. Checked paths, precedence, menu labels, the
hive validatecommand, and reload behavior against the v5 manifests and source. Checked existing Markdown link targets and section anchors.-- hive: backend=omp model=openai-codex/gpt-6.2-sol