docs: document per-block validation and legacy addon warning for porter apply#335
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: document per-block validation and legacy addon warning for porter apply#335mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
Documents the new behavior where
porter apply validate(andporter apply --validate) splits multi-app/addonporter.yamlfiles and validates each app and addon block individually, and prints a deprecation warning for addon blocks that use the legacy schema.Changes
standard/cli/command-reference/porter-apply.mdx— expanded the Validation Options section to describe single-app vs. multi-app/addon behavior and the legacy-schema deprecation warning, plus a new example forporter apply validate.applications/configuration-as-code/addons-porter-yaml.mdx— added a Validating multi-app/addon porter.yaml section covering the per-block validation flow and the legacy-addon warning.Context
Triggered by porter-dev/code#6072, which made
applyValidatewalk each app and addon block in a multi-app/addonporter.yaml, validate them individually, and emit a yellowDEPRECATION WARNINGfor legacy addon schemas instead of failing.cc @GKestenberg for review.