Configuration for Dashboard using OpenAPI spec (do no merge) #843
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.
This includes the configuration to make Dashboard OpenAPI spec. This is the version generated by swagger.
The spec misses defaults, disjunctions, enums, etc... and it adds a
dashboardv2.missing.yamlconfiguration for that.The spec is generated against generated Go dashboard in Grafana, so it gets the intermediate objects that represents the disjunction as reference instead the values that composes the disjunction. So for the POV of the generator is a normal struct :/.
Its an example of how to make it works using this approach until we have the schemas generated directly with app-sdk.