Closed
Conversation
Contributor
|
Documentation preview: |
Contributor
|
Though it doesn't address the look-and-feel concerns, I ran some validation tools against the Fleet open API specification today and I think there are indeed some issues that relate to the errors you reported in this PR. For example: Likewise by running the linter from https://github.com/wework/speccy I get: These seem like pretty minor errors so I can help debug if necessary. I've created #149990 to track their resolution. |
Contributor
Author
|
Closing because there is a new PR up at elastic/observability-docs#2715 |
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
Follows the process described in this readme to add a technical preview of the Fleet API docs.
Preview link: https://kibana_146491.docs-preview.app.elstc.co/guide/en/kibana/master/fleet-apis.html
Problems encountered when running the conversion tool
1 - Encountered
-attribute paths.'/agent_status/data'(get).parameters.[agentsIds].schemas.items is missingerror.Expand to see error details
2 - Was able to get past the validation error by running the tool with
--skip-validate-specspecified, but got quite a few messages (INFO and WARN):Expand to see error details
Problems with the output