Add provider compatibility matrix generator - #539
Draft
nikatza wants to merge 1 commit into
Draft
Conversation
hardikdr
added
the
area/switch-automation
Add a code generator under hack/provider-compatibility-matrix that statically analyzes provider packages to produce a Markdown compatibility matrix at docs/provider-compatibility.md. The tool loads provider packages via go/packages, discovers XProvider interfaces from the provider root, checks which concrete types implement them, and AST-walks each EnsureX method to find apistatus.NewUnsupportedFieldError() calls. It follows same-package call chains to collect unsupported field paths, handling inline FieldViolation literals, slice-collected helpers, and fmt.Sprintf format verbs. The rendered output is a Markdown table with per-resource rows and per-provider columns showing full (✓), partial (~), or unimplemented. Partial cells link to footnotes listing the unsupported spec fields. Resource names link into the API reference when a matching heading exists. Split the existing docs Makefile target into api-reference and compatibility-matrix, with docs depending on both. Update the api-reference config to include AccessControlList. Signed-off-by: Pujol <enric.pujol@sap.com>
nikatza
force-pushed
the
provider-matrix-markers
branch
from
September 1, 2026 07:33
dbee63b to
d3fb490
Compare
Merging this branch will increase overall coverage
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
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
2 participants
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.
Add a code generator under hack/provider-compatibility-matrix that statically analyzes provider packages to produce a Markdown compatibility matrix at docs/provider-compatibility.md.
The tool loads provider packages via go/packages, discovers XProvider interfaces from the provider root, checks which concrete types implement them, and AST-walks each EnsureX method to find apistatus.NewUnsupportedFieldError() calls. It follows same-package call chains to collect unsupported field paths, handling inline FieldViolation literals, slice-collected helpers, and fmt.Sprintf format verbs.
The rendered output is a Markdown table with per-resource rows and per-provider columns showing full (✓), partial (~), or unimplemented. Partial cells link to footnotes listing the unsupported spec fields. Resource names link into the API reference when a matching heading exists.
Split the existing docs Makefile target into api-reference and compatibility-matrix, with docs depending on both. Update the api-reference config to include AccessControlList.