[Only merge when 8.16 becomes current][8.x] Direct users to new API reference site (backport #5911) #5914
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.
Contributes to https://github.com/elastic/security-docs-internal/issues/48.
Add callouts to the asciidoc API docs to direct users to the new API reference site, in preparation for retiring the asciidoc API docs.
NOTE: The
api-kibana
variable is defined in version-specific files. In 8.15.asciidoc and 8.x.asciidoc, the variable points to the v8 branch of the API reference, which currently doesn't include Security API docs. The v8 branch is derived from the "current" Kibana branch, which is currently 8.15. This likely means that we can only backport the callouts to 8.16 once 8.16 becomes the "current" docs version.This is an automatic backport of pull request #5911 done by Mergify.