-
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
[eem] add entity definition state #191933
[eem] add entity definition state #191933
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
x-pack/plugins/observability_solution/entity_manager/server/lib/utils.ts
Show resolved
Hide resolved
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.
Overall, I think this approach looks good 👍🏼
x-pack/plugins/observability_solution/entity_manager/server/routes/enablement/check.ts
Outdated
Show resolved
Hide resolved
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Public APIs missing comments
History
To update your PR or re-run it, just comment with: |
@klacabane can you check if this needs to be backported to 8.x? |
~blocked by elastic#192004 This change adds an `includeState: boolean` option to methods querying entity definitions. When true this adds an `EntityDefinitionState` object containing all the definition components and their state (installed or not) and stats. Since this may only be used internally (eg builtin definition installation process) and for troubleshooting, `includeState` is false by default #### Testing - install a definition - call `GET kbn:/internal/entities/definition/<definition-id>?includeState=true` - check and validate the definition `state` block - manually remove transform/pipeline/template components - check and validate the definition `state` block (cherry picked from commit 2f1d0cd)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
# Backport This will backport the following commits from `main` to `8.x`: - [[eem] add entity definition state (#191933)](#191933) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Lacabane","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-09-13T07:53:50Z","message":"[eem] add entity definition state (#191933)\n\n~blocked by https://github.com/elastic/kibana/issues/192004~\r\n\r\nThis change adds an `includeState: boolean` option to methods querying\r\nentity definitions. When true this adds an `EntityDefinitionState`\r\nobject containing all the definition components and their state\r\n(installed or not) and stats. Since this may only be used internally (eg\r\nbuiltin definition installation process) and for troubleshooting,\r\n`includeState` is false by default\r\n\r\n#### Testing\r\n- install a definition\r\n- call `GET\r\nkbn:/internal/entities/definition/<definition-id>?includeState=true`\r\n- check and validate the definition `state` block\r\n- manually remove transform/pipeline/template components\r\n- check and validate the definition `state` block","sha":"2f1d0cd9b37a08bd91fc8ae8d6442cc93097f99c","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Feature:EEM","team:obs-entities"],"title":"[eem] add entity definition state","number":191933,"url":"https://github.com/elastic/kibana/pull/191933","mergeCommit":{"message":"[eem] add entity definition state (#191933)\n\n~blocked by https://github.com/elastic/kibana/issues/192004~\r\n\r\nThis change adds an `includeState: boolean` option to methods querying\r\nentity definitions. When true this adds an `EntityDefinitionState`\r\nobject containing all the definition components and their state\r\n(installed or not) and stats. Since this may only be used internally (eg\r\nbuiltin definition installation process) and for troubleshooting,\r\n`includeState` is false by default\r\n\r\n#### Testing\r\n- install a definition\r\n- call `GET\r\nkbn:/internal/entities/definition/<definition-id>?includeState=true`\r\n- check and validate the definition `state` block\r\n- manually remove transform/pipeline/template components\r\n- check and validate the definition `state` block","sha":"2f1d0cd9b37a08bd91fc8ae8d6442cc93097f99c"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/191933","number":191933,"mergeCommit":{"message":"[eem] add entity definition state (#191933)\n\n~blocked by https://github.com/elastic/kibana/issues/192004~\r\n\r\nThis change adds an `includeState: boolean` option to methods querying\r\nentity definitions. When true this adds an `EntityDefinitionState`\r\nobject containing all the definition components and their state\r\n(installed or not) and stats. Since this may only be used internally (eg\r\nbuiltin definition installation process) and for troubleshooting,\r\n`includeState` is false by default\r\n\r\n#### Testing\r\n- install a definition\r\n- call `GET\r\nkbn:/internal/entities/definition/<definition-id>?includeState=true`\r\n- check and validate the definition `state` block\r\n- manually remove transform/pipeline/template components\r\n- check and validate the definition `state` block","sha":"2f1d0cd9b37a08bd91fc8ae8d6442cc93097f99c"}}]}] BACKPORT--> Co-authored-by: Kevin Lacabane <[email protected]>
blocked by #192004This change adds an
includeState: boolean
option to methods querying entity definitions. When true this adds anEntityDefinitionState
object containing all the definition components and their state (installed or not) and stats. Since this may only be used internally (eg builtin definition installation process) and for troubleshooting,includeState
is false by defaultTesting
GET kbn:/internal/entities/definition/<definition-id>?includeState=true
state
blockstate
block