[Fleet] Single agent migration UI#222111
Conversation
|
Pinging @elastic/fleet (Team:Fleet) |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
MichelLosier
left a comment
There was a problem hiding this comment.
Looks good! Just a few things to consider, blockers are the items on the proxyUrlLabel i18n id, and url validation.
x-pack/platform/plugins/shared/fleet/common/types/rest_spec/agent.ts
Outdated
Show resolved
Hide resolved
...orm/plugins/shared/fleet/public/applications/fleet/sections/agents/agent_list_page/index.tsx
Show resolved
Hide resolved
...ublic/applications/fleet/sections/agents/agent_list_page/components/migrate_agent_flyout.tsx
Outdated
Show resolved
Hide resolved
...ublic/applications/fleet/sections/agents/agent_list_page/components/migrate_agent_flyout.tsx
Outdated
Show resolved
Hide resolved
…h server schema, changed URL check to use zod
…m/Supplementing/kibana into feature-single-agent-migration-ui
…m/Supplementing/kibana into feature-single-agent-migration-ui
MichelLosier
left a comment
There was a problem hiding this comment.
Thanks for the updates! Getting close, just need to remove the console log, and maybe double check the client side guard against fleet-server migrations.
x-pack/platform/plugins/shared/fleet/server/services/agents/actions.ts
Outdated
Show resolved
Hide resolved
...ublic/applications/fleet/sections/agents/agent_list_page/components/migrate_agent_flyout.tsx
Outdated
Show resolved
Hide resolved
...t/public/applications/fleet/sections/agents/agent_list_page/components/table_row_actions.tsx
Show resolved
Hide resolved
.../applications/fleet/sections/agents/agent_list_page/components/migrate_agent_flyout.test.tsx
Outdated
Show resolved
Hide resolved
...ublic/applications/fleet/sections/agents/agent_list_page/components/migrate_agent_flyout.tsx
Outdated
Show resolved
Hide resolved
MichelLosier
left a comment
There was a problem hiding this comment.
Thanks for the changes, LGTM!
...t/public/applications/fleet/sections/agents/agent_list_page/components/table_row_actions.tsx
Outdated
Show resolved
Hide resolved
…t is still enrolling;
|
@elasticmachine merge upstream |
…m/Supplementing/kibana into feature-single-agent-migration-ui
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
History
|
## Summary Closes elastic#217616 Adds UI elements to support migrating a single agent to another cluster as a follow up to [this PR](elastic#220601) - Allows a user to choose an agent to migrate from the actions menu and requires an `enrollment token` and `remote cluster url` - Leverages the new migrate endpoint to create the action - Tamper protected and fleet-agents are not allowed to be migrated at this time, and the option will not exist in the menu https://github.com/user-attachments/assets/19064b2d-8e1c-465e-af10-e7ba242188ec ### 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) ### Identify risks N/A ## Release Note - Added the ability to migrate a single agent to another cluster via the actions menu in Fleet. Users can enter a remote cluster URL and enrollment token, as well as customize additional parameters in order to migrate an agent. --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Summary
Closes #217616
Adds UI elements to support migrating a single agent to another cluster as a follow up to this PR
enrollment tokenandremote cluster urlScreen.Recording.2025-06-02.at.2.55.09.PM.mov
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesIdentify risks
N/A
Release Note