-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[DOCS] Consolidate and clean up Kibana settings (part 1) #214934
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
Merged
Merged
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
This was referenced Mar 18, 2025
Contributor
|
Pinging @elastic/kibana-docs (Team:Docs) |
Contributor
💚 Build Succeeded
|
alaudazzi
approved these changes
Mar 18, 2025
Contributor
alaudazzi
left a comment
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.
LGTM
Contributor
|
Starting backport for target branches: 9.0 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Mar 18, 2025
) (cherry picked from commit 3b2df89)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Mar 18, 2025
…) (#215048) # Backport This will backport the following commits from `main` to `9.0`: - [[DOCS] Consolidate and clean up Kibana settings (part 1) (#214934)](#214934) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-03-18T18:37:40Z","message":"[DOCS] Consolidate and clean up Kibana settings (part 1) (#214934)","sha":"3b2df8935b7ab386a7b94df5f14737fc1b9b0307","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","backport:version","v9.1.0","v9.0.1"],"title":"[DOCS] Consolidate and clean up Kibana settings (part 1)","number":214934,"url":"https://github.com/elastic/kibana/pull/214934","mergeCommit":{"message":"[DOCS] Consolidate and clean up Kibana settings (part 1) (#214934)","sha":"3b2df8935b7ab386a7b94df5f14737fc1b9b0307"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214934","number":214934,"mergeCommit":{"message":"[DOCS] Consolidate and clean up Kibana settings (part 1) (#214934)","sha":"3b2df8935b7ab386a7b94df5f14737fc1b9b0307"}},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Lisa Cawley <[email protected]>
kilfoyle
added a commit
that referenced
this pull request
Mar 19, 2025
This updates the versioning tags in the Alert and Action settings yaml file to use `all` instead of `ga`. I guess the former makes more sense since these settings aren't newly GAed. The PR also makes a couple of very minor content changes based on #214934
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Mar 19, 2025
This updates the versioning tags in the Alert and Action settings yaml file to use `all` instead of `ga`. I guess the former makes more sense since these settings aren't newly GAed. The PR also makes a couple of very minor content changes based on elastic#214934 (cherry picked from commit 5d6bed8)
kibanamachine
added a commit
that referenced
this pull request
Mar 19, 2025
# Backport This will backport the following commits from `main` to `9.0`: - [Small fixes for alert & actions yaml file (#215218)](#215218) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"David Kilfoyle","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-03-19T18:19:53Z","message":"Small fixes for alert & actions yaml file (#215218)\n\nThis updates the versioning tags in the Alert and Action settings yaml\nfile to use `all` instead of `ga`. I guess the former makes more sense\nsince these settings aren't newly GAed.\n\n\nThe PR also makes a couple of very minor content changes based on\nhttps://github.com//pull/214934","sha":"5d6bed8479bfad14b7ac5c0b98cb535527dcf94b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","backport:version","v9.1.0","v9.0.1"],"title":"Small fixes for alert & actions yaml file","number":215218,"url":"https://github.com/elastic/kibana/pull/215218","mergeCommit":{"message":"Small fixes for alert & actions yaml file (#215218)\n\nThis updates the versioning tags in the Alert and Action settings yaml\nfile to use `all` instead of `ga`. I guess the former makes more sense\nsince these settings aren't newly GAed.\n\n\nThe PR also makes a couple of very minor content changes based on\nhttps://github.com//pull/214934","sha":"5d6bed8479bfad14b7ac5c0b98cb535527dcf94b"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215218","number":215218,"mergeCommit":{"message":"Small fixes for alert & actions yaml file (#215218)\n\nThis updates the versioning tags in the Alert and Action settings yaml\nfile to use `all` instead of `ga`. I guess the former makes more sense\nsince these settings aren't newly GAed.\n\n\nThe PR also makes a couple of very minor content changes based on\nhttps://github.com//pull/214934","sha":"5d6bed8479bfad14b7ac5c0b98cb535527dcf94b"}}]}] BACKPORT--> Co-authored-by: David Kilfoyle <[email protected]>
clintandrewhall
pushed a commit
to clintandrewhall/kibana
that referenced
this pull request
Mar 20, 2025
clintandrewhall
pushed a commit
to clintandrewhall/kibana
that referenced
this pull request
Mar 20, 2025
This updates the versioning tags in the Alert and Action settings yaml file to use `all` instead of `ga`. I guess the former makes more sense since these settings aren't newly GAed. The PR also makes a couple of very minor content changes based on elastic#214934
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Mar 22, 2025
JoseLuisGJ
pushed a commit
to JoseLuisGJ/kibana
that referenced
this pull request
Mar 24, 2025
This updates the versioning tags in the Alert and Action settings yaml file to use `all` instead of `ga`. I guess the former makes more sense since these settings aren't newly GAed. The PR also makes a couple of very minor content changes based on elastic#214934
cqliu1
pushed a commit
to cqliu1/kibana
that referenced
this pull request
Mar 31, 2025
cqliu1
pushed a commit
to cqliu1/kibana
that referenced
this pull request
Mar 31, 2025
This updates the versioning tags in the Alert and Action settings yaml file to use `all` instead of `ga`. I guess the former makes more sense since these settings aren't newly GAed. The PR also makes a couple of very minor content changes based on elastic#214934
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport:version
Backport to applied version labels
docs
release_note:skip
Skip the PR/issue when compiling release notes
Team:Docs
v9.0.0
v9.0.1
v9.1.0
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
Relates to elastic/elasticsearch#125000
This PR cleans up the Kibana setting pages as follows:
The explanation of the cloud icon (e.g. in https://docs-v3-preview.elastic.dev/elastic/kibana/pull/214934/reference/configuration-reference/general-settings) is maybe overkill, but the hover-text alone was insufficient IMO). The long-term vision for settings in the new docs system can be viewed in elastic/docs-builder#760
Further movement of the content out of the Cloud-specific page (ideally so that page can be retired) is required, but I think that should maybe go into a second PR just to get some of these changes in as soon as possible.