fix: skip deploy-config-schema validate for ClusterContext file#41
Merged
jorisjonkers-dev-agents[bot] merged 1 commit intoJul 9, 2026
Conversation
jorisjonkers-dev-agents
Bot
added
the
type: bug
jorisjonkers-dev-agents
Bot
deleted the
fix/remove-cluster-context-deploy-config-validate
branch
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
1 participant
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.
Removes the incorrect call to
deploy-config-schema validate "$context_file"in deploy-artifact/run.sh step (6).The cluster-context-public.yml file has kind=ClusterContext, not a deploy-config. Using the
validateCLI subcommand on it causes the CLI to fall back to the deploy-config schema, producing spurious E_SCHEMA errors for fields like access_intent, cluster, exposure_intent, etc. that don't exist in the deploy-config schema.The context is already validated by homelab-inventory before being published (using the programmatic validateClusterContext API, not the CLI). The fix reduces step (6) to a presence-check only: fail if the file is absent, but do not schema-validate it.