feat(parsers): enrich PreflightConfigFile field docs for cvs man - #341
Open
speriaswamy-amd wants to merge 1 commit into
Open
Conversation
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.
Part 8 of 14 in a stack for AIMVT-276.
Base: #340.
Why
cvs manrenders each field'sdescription/examplesfrom its pydanticmodel.
PreflightConfigFilealready existed before this ticket, but most ofits fields had thin or missing descriptions and no examples, so
cvs manoutput for the preflight suite would be far less useful than for the new
rccl/health/megatron schemas.
What changed
descriptionandexamplesonPreflightConfigFile'snested field groups (rdma, node_check, connectivity, etc.), sourced from
the actual behavior in the preflight test code — no schema shape changes.