Adding APIGroups back to the schema #230
Merged
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.
Overview
Related to rancher/rancher#45955. Previous changes changed the order that schemas were evaluated in (used to be
models
, thenServerGroupsAndResources
, is nowServerGroupsAndResources
, thenmodels
). The APIGroups resource, which is not itself a server group/resource, but is a model, was omitted because of this. This re-adds this custom schema first (so that the description later on can fill in more detail), making the endpoint visible again in steve.Solution Detail
BaseSchema
to theapigroup
package.BaseSchema
forapigroup
.addDescription
will add a description for this schema.