-
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
Added versioning to inventory_view_saved_object #207007
Added versioning to inventory_view_saved_object #207007
Conversation
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
Pinging @elastic/kibana-core (Team:Core) |
… src/core/server/integration_tests/ci_checks'
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. code only
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 (code review only)
💛 Build succeeded, but was flaky
Failed CI Steps
Test Failures
Metrics [docs]
History
|
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.
tsconfig changes LGTM
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.
Saved object changes LGTM.
Should we add notes to all versions of kibana between v8.10 and oldest version available for backport describing this bug?
Adding it to known issues for those releases would be optimal if it's possible.
The other alternative is to highlight the bug in the current release notes and calling it out in the inventory view API public docs.
Friendly reminder: Looks like this PR hasn’t been backported yet. |
3 similar comments
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
7 similar comments
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
## Summary Fixes elastic#187254 Strict checks on the attribute `legend.steps` was added to the inventory view API in v8.10 (elastic#160852), but they were not defined in the saved object type for that data, resulting in older versions migrating bad data, and being unable to use the API. This PR adds versioning to the Inventory view saved object type that constrains legend.steps to between 2 and 18, per the strict typing added in elastic#160852 #### Open questions Should we add notes to all versions of kibana between v8.10 and oldest version available for backport describing this bug? ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit a108c63) # Conflicts: # x-pack/solutions/observability/plugins/infra/tsconfig.json
## Summary Fixes elastic#187254 Strict checks on the attribute `legend.steps` was added to the inventory view API in v8.10 (elastic#160852), but they were not defined in the saved object type for that data, resulting in older versions migrating bad data, and being unable to use the API. This PR adds versioning to the Inventory view saved object type that constrains legend.steps to between 2 and 18, per the strict typing added in elastic#160852 #### Open questions Should we add notes to all versions of kibana between v8.10 and oldest version available for backport describing this bug? ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit a108c63) # Conflicts: # x-pack/plugins/observability_solution/infra/server/saved_objects/inventory_view/inventory_view_saved_object.test.ts # x-pack/plugins/observability_solution/infra/tsconfig.json
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
1 similar comment
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
) # Backport This will backport the following commits from `main` to `8.x`: - [Added versioning to inventory_view_saved_object (#207007)](#207007) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bryce Buchanan","email":"75274611+bryce-b@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-27T18:09:32Z","message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a108c632a459240f9c27262395e2584f92d43779","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:fix","backport missing","v9.0.0","Team:obs-ux-infra_services"],"title":"Added versioning to inventory_view_saved_object","number":207007,"url":"https://github.com/elastic/kibana/pull/207007","mergeCommit":{"message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a108c632a459240f9c27262395e2584f92d43779"}},"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/207007","number":207007,"mergeCommit":{"message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a108c632a459240f9c27262395e2584f92d43779"}}]}] BACKPORT-->
…1632) # Backport This will backport the following commits from `main` to `8.18`: - [Added versioning to inventory_view_saved_object (#207007)](#207007) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bryce Buchanan","email":"75274611+bryce-b@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-27T18:09:32Z","message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a108c632a459240f9c27262395e2584f92d43779","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:fix","backport missing","v9.0.0","Team:obs-ux-infra_services"],"title":"Added versioning to inventory_view_saved_object","number":207007,"url":"https://github.com/elastic/kibana/pull/207007","mergeCommit":{"message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a108c632a459240f9c27262395e2584f92d43779"}},"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/207007","number":207007,"mergeCommit":{"message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a108c632a459240f9c27262395e2584f92d43779"}}]}] BACKPORT-->
…1634) # Backport This will backport the following commits from `main` to `8.17`: - [Added versioning to inventory_view_saved_object (#207007)](#207007) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bryce Buchanan","email":"75274611+bryce-b@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-27T18:09:32Z","message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a108c632a459240f9c27262395e2584f92d43779","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:fix","backport missing","v9.0.0","Team:obs-ux-infra_services"],"title":"Added versioning to inventory_view_saved_object","number":207007,"url":"https://github.com/elastic/kibana/pull/207007","mergeCommit":{"message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a108c632a459240f9c27262395e2584f92d43779"}},"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/207007","number":207007,"mergeCommit":{"message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"a108c632a459240f9c27262395e2584f92d43779"}}]}] BACKPORT-->
Summary
Fixes #187254
Strict checks on the attribute
legend.steps
was added to the inventory view API in v8.10 (#160852), but they were not defined in thesaved object type for that data, resulting in older versions migrating bad data, and being unable to use the API. This PR adds versioning to the Inventory view saved object type that constrains legend.steps to between 2 and 18, per the strict typing added in #160852
Open questions
Should we add notes to all versions of kibana between v8.10 and oldest version available for backport describing this bug?Notes were added here: https://github.com/elastic/kibana/pull/207629/files
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:*
label is applied per the guidelines