[Console] Update Elasticsearch specification metamodel #193239
Merged
Conversation
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
pquentin
added
Feature:Console
|
Pinging @elastic/kibana-management (Team:Kibana Management) |
|
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
To update your PR or re-run it, just comment with: |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 19, 2024
## Summary As mentioned in elastic#163335, the Elasticsearch specification metamodel is copied into Kibana, not imported. I don't know how to fix the original issue, so this pull request only updates the file, one year later. ### Checklist - [x] I checked that `node scripts/generate_console_definitions.js --source ../elasticsearch-specification/ --emptyDest` still works. Co-authored-by: Elastic Machine <[email protected]> (cherry picked from commit f6cff85)
💚 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
Sep 19, 2024
#193405) # Backport This will backport the following commits from `main` to `8.x`: - [[Console] Update Elasticsearch specification metamodel (#193239)](#193239) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Quentin Pradet","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-09-19T10:31:13Z","message":"[Console] Update Elasticsearch specification metamodel (#193239)\n\n## Summary\r\n\r\nAs mentioned in #163335, the\r\nElasticsearch specification metamodel is copied into Kibana, not\r\nimported. I don't know how to fix the original issue, so this pull\r\nrequest only updates the file, one year later.\r\n\r\n### Checklist\r\n\r\n- [x] I checked that `node scripts/generate_console_definitions.js\r\n--source ../elasticsearch-specification/ --emptyDest` still works.\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"f6cff85c8d0ae4b32fbced558e831465d844e2ee","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor","v8.16.0"],"title":"[Console] Update Elasticsearch specification metamodel","number":193239,"url":"https://github.com/elastic/kibana/pull/193239","mergeCommit":{"message":"[Console] Update Elasticsearch specification metamodel (#193239)\n\n## Summary\r\n\r\nAs mentioned in #163335, the\r\nElasticsearch specification metamodel is copied into Kibana, not\r\nimported. I don't know how to fix the original issue, so this pull\r\nrequest only updates the file, one year later.\r\n\r\n### Checklist\r\n\r\n- [x] I checked that `node scripts/generate_console_definitions.js\r\n--source ../elasticsearch-specification/ --emptyDest` still works.\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"f6cff85c8d0ae4b32fbced558e831465d844e2ee"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/193239","number":193239,"mergeCommit":{"message":"[Console] Update Elasticsearch specification metamodel (#193239)\n\n## Summary\r\n\r\nAs mentioned in #163335, the\r\nElasticsearch specification metamodel is copied into Kibana, not\r\nimported. I don't know how to fix the original issue, so this pull\r\nrequest only updates the file, one year later.\r\n\r\n### Checklist\r\n\r\n- [x] I checked that `node scripts/generate_console_definitions.js\r\n--source ../elasticsearch-specification/ --emptyDest` still works.\r\n\r\nCo-authored-by: Elastic Machine <[email protected]>","sha":"f6cff85c8d0ae4b32fbced558e831465d844e2ee"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Quentin Pradet <[email protected]>
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
As mentioned in #163335, the Elasticsearch specification metamodel is copied into Kibana, not imported. I don't know how to fix the original issue, so this pull request only updates the file, one year later.
Checklist
node scripts/generate_console_definitions.js --source ../elasticsearch-specification/ --emptyDeststill works.For maintainers