Skip to content
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

Merged
merged 10 commits into from
Jan 27, 2025

Conversation

bryce-b
Copy link
Contributor

@bryce-b bryce-b commented Jan 16, 2025

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 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 #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.

  • Unit or functional tests were updated or added to match the most common scenarios
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines

@bryce-b bryce-b added release_note:fix backport:all-open Backport to all branches that could still receive a release labels Jan 16, 2025
@bryce-b bryce-b marked this pull request as ready for review January 16, 2025 21:44
@bryce-b bryce-b requested a review from a team as a code owner January 16, 2025 21:44
@bryce-b bryce-b added core-apm Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team labels Jan 16, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

@bryce-b bryce-b added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc and removed core-apm labels Jan 16, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@elastic-vault-github-plugin-prod elastic-vault-github-plugin-prod bot requested a review from a team as a code owner January 16, 2025 21:54
@elastic-vault-github-plugin-prod elastic-vault-github-plugin-prod bot requested a review from a team as a code owner January 16, 2025 22:18
Copy link
Contributor

@crespocarlos crespocarlos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. code only

Copy link
Member

@jennypavlova jennypavlova left a 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)

@bryce-b bryce-b enabled auto-merge (squash) January 23, 2025 16:45
@elasticmachine
Copy link
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] Jest Tests #7 / form fields calls onSubmit with case fields
  • [job] [logs] Jest Tests #7 / useDeleteCases invalidates the queries correctly

Metrics [docs]

✅ unchanged

History

Copy link
Contributor

@yngrdyn yngrdyn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tsconfig changes LGTM

Copy link
Contributor

@TinaHeiligers TinaHeiligers left a 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.

@bryce-b bryce-b merged commit a108c63 into elastic:main Jan 27, 2025
8 checks passed
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 207007 locally

3 similar comments
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 207007 locally

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 207007 locally

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 207007 locally

@crespocarlos crespocarlos removed the backport:all-open Backport to all branches that could still receive a release label Feb 6, 2025
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 207007 locally

7 similar comments
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 207007 locally

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 207007 locally

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 207007 locally

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 207007 locally

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 207007 locally

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 207007 locally

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 207007 locally

bryce-b added a commit to bryce-b/kibana that referenced this pull request Feb 18, 2025
## 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
bryce-b added a commit to bryce-b/kibana that referenced this pull request Feb 18, 2025
## 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
@bryce-b
Copy link
Contributor Author

bryce-b commented Feb 18, 2025

💔 Some backports could not be created

Status Branch Result
8.x
8.18
8.17
7.17 Conflict resolution was aborted by the user

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 207007

Questions ?

Please refer to the Backport tool documentation

@kibanamachine
Copy link
Contributor

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
@kibanamachine
Copy link
Contributor

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.

bryce-b added a commit that referenced this pull request Feb 21, 2025
)

# 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-->
bryce-b added a commit that referenced this pull request Feb 21, 2025
…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-->
bryce-b added a commit that referenced this pull request Feb 21, 2025
…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-->
@kibanamachine kibanamachine added v8.18.0 v8.17.3 and removed backport missing Added to PRs automatically when the are determined to be missing a backport. labels Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:fix Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team v8.17.3 v8.18.0 v8.19.0 v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

500 when loading Observability Infrastructure Inventory view after upgrading to 8.10.0 or higher
7 participants