[9.2][Fleet] Remove feature flag and add license gate for Agent migrations (#237342)#239556
Merged
juliaElastic merged 4 commits intoelastic:9.2from Oct 20, 2025
Merged
Conversation
…elastic#237342) Closes elastic/ingest-dev#6165 Closes elastic/ingest-dev#6164 This PR removes the experimental FF in Fleet UI as well as the endpoints, and also gates both sides behind the enterprise license. Also removed unit tests that checked against the feature flag as they are no longer needed. - So the user is aware it exists, but cannot interact, the 'migrate' button is shown but disabled for both single agents and bulk actions in Fleet UI - The endpoints for both perform a check and return a `403` letting the user know they need to upgrade their license if they do not have the correct license. - Added unit tests for both handlers to confirm license check works as intended. NOTE: since the api integration tests run on an enterprise license by default, it would require additional configuration in order to test, and since the handlers have the tests, we dont need to add the redundancy. Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [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 - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. N/A --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
juliaElastic
added
backport
botelastic
bot
added
the
Team:Fleet
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
Contributor
Author
|
/ci |
jillguyonnet
approved these changes
Oct 17, 2025
Contributor
|
This backport is failing on some tests. Looks like the tests depend on changes from #237189 so I'm going to kick off a backport of that one to 9.2 as well, and hopefully this will pass after that backport gets merged in. |
Contributor
💔 Build Failed
Failed CI Steps
Test Failures
Metrics [docs]Async chunks
Page load bundle
History
|
This was referenced Jan 9, 2026
Merged
vishaangelova
added a commit
that referenced
this pull request
Jan 12, 2026
…248655) ## Summary This PR adds a release note entry for the Agent migrations feature (the feature flag was removed in 9.2 with #239556). Contributes to elastic/docs-content#4575 ## Context The Agent migrate APIs and actions were added to Fleet Server (elastic/fleet-server#4786), Elastic Agent (elastic/elastic-agent#8014), and Kibana (#220601) in 9.1.0 but were gated behind a feature flag (#224143) in 9.1.0. The feature flag was removed in 9.2 with #239556. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [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 - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks N/A --------- Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jan 12, 2026
…lastic#248655) ## Summary This PR adds a release note entry for the Agent migrations feature (the feature flag was removed in 9.2 with elastic#239556). Contributes to elastic/docs-content#4575 ## Context The Agent migrate APIs and actions were added to Fleet Server (elastic/fleet-server#4786), Elastic Agent (elastic/elastic-agent#8014), and Kibana (elastic#220601) in 9.1.0 but were gated behind a feature flag (elastic#224143) in 9.1.0. The feature flag was removed in 9.2 with elastic#239556. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [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 - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks N/A --------- Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> (cherry picked from commit 92ffd74)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jan 12, 2026
…lastic#248655) ## Summary This PR adds a release note entry for the Agent migrations feature (the feature flag was removed in 9.2 with elastic#239556). Contributes to elastic/docs-content#4575 ## Context The Agent migrate APIs and actions were added to Fleet Server (elastic/fleet-server#4786), Elastic Agent (elastic/elastic-agent#8014), and Kibana (elastic#220601) in 9.1.0 but were gated behind a feature flag (elastic#224143) in 9.1.0. The feature flag was removed in 9.2 with elastic#239556. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [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 - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks N/A --------- Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> (cherry picked from commit 92ffd74)
kibanamachine
added a commit
that referenced
this pull request
Jan 12, 2026
…tes (#248655) (#248758) # Backport This will backport the following commits from `main` to `9.3`: - [[DOCS] Add entry for Agent migrations feature in 9.2 release notes (#248655)](#248655) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Visha Angelova","email":"91186315+vishaangelova@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-01-12T19:38:33Z","message":"[DOCS] Add entry for Agent migrations feature in 9.2 release notes (#248655)\n\n## Summary\n\nThis PR adds a release note entry for the Agent migrations feature (the\nfeature flag was removed in 9.2 with\nhttps://github.com//pull/239556).\n\nContributes to https://github.com/elastic/docs-content/issues/4575\n\n## Context\n\nThe Agent migrate APIs and actions were added to Fleet Server\n(elastic/fleet-server#4786), Elastic Agent\n(elastic/elastic-agent#8014), and Kibana\n(#220601) in 9.1.0 but were gated\nbehind a feature flag (#224143) in\n9.1.0. The feature flag was removed in 9.2 with\nhttps://github.com//pull/239556.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nN/A\n\n---------\n\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>","sha":"92ffd7422a1a8e3545196b67d4fedf290a06c0df","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","backport:version","v9.2.0","v9.3.0","v9.4.0"],"title":"[DOCS] Add entry for Agent migrations feature in 9.2 release notes","number":248655,"url":"https://github.com/elastic/kibana/pull/248655","mergeCommit":{"message":"[DOCS] Add entry for Agent migrations feature in 9.2 release notes (#248655)\n\n## Summary\n\nThis PR adds a release note entry for the Agent migrations feature (the\nfeature flag was removed in 9.2 with\nhttps://github.com//pull/239556).\n\nContributes to https://github.com/elastic/docs-content/issues/4575\n\n## Context\n\nThe Agent migrate APIs and actions were added to Fleet Server\n(elastic/fleet-server#4786), Elastic Agent\n(elastic/elastic-agent#8014), and Kibana\n(#220601) in 9.1.0 but were gated\nbehind a feature flag (#224143) in\n9.1.0. The feature flag was removed in 9.2 with\nhttps://github.com//pull/239556.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nN/A\n\n---------\n\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>","sha":"92ffd7422a1a8e3545196b67d4fedf290a06c0df"}},"sourceBranch":"main","suggestedTargetBranches":["9.2","9.3"],"targetPullRequestStates":[{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/248655","number":248655,"mergeCommit":{"message":"[DOCS] Add entry for Agent migrations feature in 9.2 release notes (#248655)\n\n## Summary\n\nThis PR adds a release note entry for the Agent migrations feature (the\nfeature flag was removed in 9.2 with\nhttps://github.com//pull/239556).\n\nContributes to https://github.com/elastic/docs-content/issues/4575\n\n## Context\n\nThe Agent migrate APIs and actions were added to Fleet Server\n(elastic/fleet-server#4786), Elastic Agent\n(elastic/elastic-agent#8014), and Kibana\n(#220601) in 9.1.0 but were gated\nbehind a feature flag (#224143) in\n9.1.0. The feature flag was removed in 9.2 with\nhttps://github.com//pull/239556.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nN/A\n\n---------\n\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>","sha":"92ffd7422a1a8e3545196b67d4fedf290a06c0df"}}]}] BACKPORT--> Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
kibanamachine
added a commit
that referenced
this pull request
Jan 12, 2026
…tes (#248655) (#248757) # Backport This will backport the following commits from `main` to `9.2`: - [[DOCS] Add entry for Agent migrations feature in 9.2 release notes (#248655)](#248655) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Visha Angelova","email":"91186315+vishaangelova@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-01-12T19:38:33Z","message":"[DOCS] Add entry for Agent migrations feature in 9.2 release notes (#248655)\n\n## Summary\n\nThis PR adds a release note entry for the Agent migrations feature (the\nfeature flag was removed in 9.2 with\nhttps://github.com//pull/239556).\n\nContributes to https://github.com/elastic/docs-content/issues/4575\n\n## Context\n\nThe Agent migrate APIs and actions were added to Fleet Server\n(elastic/fleet-server#4786), Elastic Agent\n(elastic/elastic-agent#8014), and Kibana\n(#220601) in 9.1.0 but were gated\nbehind a feature flag (#224143) in\n9.1.0. The feature flag was removed in 9.2 with\nhttps://github.com//pull/239556.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nN/A\n\n---------\n\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>","sha":"92ffd7422a1a8e3545196b67d4fedf290a06c0df","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","backport:version","v9.2.0","v9.3.0","v9.4.0"],"title":"[DOCS] Add entry for Agent migrations feature in 9.2 release notes","number":248655,"url":"https://github.com/elastic/kibana/pull/248655","mergeCommit":{"message":"[DOCS] Add entry for Agent migrations feature in 9.2 release notes (#248655)\n\n## Summary\n\nThis PR adds a release note entry for the Agent migrations feature (the\nfeature flag was removed in 9.2 with\nhttps://github.com//pull/239556).\n\nContributes to https://github.com/elastic/docs-content/issues/4575\n\n## Context\n\nThe Agent migrate APIs and actions were added to Fleet Server\n(elastic/fleet-server#4786), Elastic Agent\n(elastic/elastic-agent#8014), and Kibana\n(#220601) in 9.1.0 but were gated\nbehind a feature flag (#224143) in\n9.1.0. The feature flag was removed in 9.2 with\nhttps://github.com//pull/239556.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nN/A\n\n---------\n\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>","sha":"92ffd7422a1a8e3545196b67d4fedf290a06c0df"}},"sourceBranch":"main","suggestedTargetBranches":["9.2","9.3"],"targetPullRequestStates":[{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/248655","number":248655,"mergeCommit":{"message":"[DOCS] Add entry for Agent migrations feature in 9.2 release notes (#248655)\n\n## Summary\n\nThis PR adds a release note entry for the Agent migrations feature (the\nfeature flag was removed in 9.2 with\nhttps://github.com//pull/239556).\n\nContributes to https://github.com/elastic/docs-content/issues/4575\n\n## Context\n\nThe Agent migrate APIs and actions were added to Fleet Server\n(elastic/fleet-server#4786), Elastic Agent\n(elastic/elastic-agent#8014), and Kibana\n(#220601) in 9.1.0 but were gated\nbehind a feature flag (#224143) in\n9.1.0. The feature flag was removed in 9.2 with\nhttps://github.com//pull/239556.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nN/A\n\n---------\n\nCo-authored-by: florent-leborgne <florent.leborgne@elastic.co>","sha":"92ffd7422a1a8e3545196b67d4fedf290a06c0df"}}]}] BACKPORT--> Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
tsullivan
pushed a commit
that referenced
this pull request
Jan 12, 2026
…248655) ## Summary This PR adds a release note entry for the Agent migrations feature (the feature flag was removed in 9.2 with #239556). Contributes to elastic/docs-content#4575 ## Context The Agent migrate APIs and actions were added to Fleet Server (elastic/fleet-server#4786), Elastic Agent (elastic/elastic-agent#8014), and Kibana (#220601) in 9.1.0 but were gated behind a feature flag (#224143) in 9.1.0. The feature flag was removed in 9.2 with #239556. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [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 - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] 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) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks N/A --------- Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
This was referenced Jan 13, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Backport #237342 to 9.2
tested on pr cloud deployment
