-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[OAS] Remove elastic-api-version
from stateful spec
#197968
Closed
jloleysens
wants to merge
17
commits into
elastic:main
from
jloleysens:oas/remove-elastic-api-from-stateful-doc
Closed
Changes from 3 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
30040c9
"make api-docs" do everything incl overlays and remove some of the do…
jloleysens e7b575d
no extension
jloleysens 4fec6f3
updated file output
jloleysens 068ca44
added echoes when rendering previews
jloleysens 2996047
npm install
jloleysens 9978403
package.json to oas_docs
jloleysens 6a97460
move sed
jloleysens d11c73d
[CI] Auto-commit changed files from 'make api-docs'
kibanamachine 82172c5
cd and log
jloleysens b9e394f
Merge branch 'main' into oas/remove-elastic-api-from-stateful-doc
jloleysens b6dd030
[CI] Auto-commit changed files from 'make api-docs'
kibanamachine dca423d
Merge branch 'main' into oas/remove-elastic-api-from-stateful-doc
jloleysens b91fd9d
Merge branch 'main' into oas/remove-elastic-api-from-stateful-doc
jloleysens 7656280
Merge branch 'main' into oas/remove-elastic-api-from-stateful-doc
jloleysens c180177
[CI] Auto-commit changed files from 'make api-docs'
kibanamachine d4709cb
Update capture_oas_snapshot.sh
jloleysens 91cfe8f
Update capture_oas_snapshot.sh
jloleysens File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lukeelmers this is where we remove the
Elastic-Api-Version
from the stateful bundles. For now I think this should be OK as, in future, we might choose to introduce them there more formally.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks! does it need to be there in serverless too... it feels like we could remove it in both places, right? (since it looks like this is the one that's in the
content-type
which afaik nobody needs to actually include)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my concern for stateful is that it will be confusing as we have not formally/publicly explained how the dual date/stack versioning works there.
my concern for serverless is that it is just redundant and also a bit confusing since content-type does not dictate api version (unless I missed something)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My understanding is it is intended to be used for grouping our serverless versions. Until that strategy changes from docs side I don't think we should remove it for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Relates to elastic/docs-content#142 As soon as we start having multiple valid in-support elastic-api-version values in stateful or serverless, we'll need to be able to differentiate their impact on the requests and responses.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whenever we're ready to document that, it can be added to the API docs in a topic similar to https://www.elastic.co/docs/api/doc/kibana/topic/topic-kibana-spaces, which we add via
kibana/oas_docs/overlays/kibana.overlays.yaml
Line 11 in d601e23