Repository navigation
docs: correct config keys and stack output paths across component docs - #14
Merged
AdamNowotny merged 1 commit intoSep 21, 2026
Conversation
Collaborator
|
Docs verified — all config-key and output-path corrections check out against the source and are correct:
One blocker: the branch conflicts with |
awdemos
force-pushed
the
docs/config-keys-and-output-paths
branch
from
September 17, 2026 17:11
ba079f5 to
d2aee92
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Corrects component docs that instructed wrong, dead, or stale configuration keys and stack-output paths (each verified against the code):
invokeai:enable→invokeai:enabled(the code readsenabledviaconfig.isEnabled; following the doc deployed nothing)bitcoin-core:maxconnections→bitcoin-knots:maxconnectionsmempool:hostname→ the real required keysmempool:frontend/hostnameandmempool:backend/hostnamepulumi set kubeai:enableMonitoring true→ the real gate:prometheus:enabled+prometheus:enableComponentMonitoringnextcloud:storageSize(second line overwrote the first) →nextcloud:db/storageSize; "PostgreSQL" → MariaDB; documented the requirednextcloud:trustedProxiesandnextcloud:groupProvisioningWhitelistkeys; fixed the OAuth snippet using$DISCOVERY_URLbefore it was defined.media.*/.ai.*jq prefixes onpulumi stack output(stacks export top-levelclusterUrls/endpoints)HIP_VISIBLE_DEVICES/CUDA_VISIBLE_DEVICES(never read by the code); documented the AMD keys that are actually read (HSA_OVERRIDE_GFX_VERSION,HCC_AMDGPU_TARGETS)Verification
Markdown-only — no tests needed per project convention. Every key/path cross-checked against the component source before editing.