Skip to content

[Fleet] Only sync integrations installed from registry#239567

Merged
jillguyonnet merged 1 commit intoelastic:mainfrom
jillguyonnet:fleet/228570-disallow-custom-integration-syncing
Oct 17, 2025
Merged

[Fleet] Only sync integrations installed from registry#239567
jillguyonnet merged 1 commit intoelastic:mainfrom
jillguyonnet:fleet/228570-disallow-custom-integration-syncing

Conversation

@jillguyonnet
Copy link
Copy Markdown
Member

@jillguyonnet jillguyonnet commented Oct 17, 2025 •
edited
Loading

Summary

Closes #228570

This PR limits integration syncing in Fleet to packages installed from the registry. Other packages won't be picked up or shown in the sync status.

To test:

  1. Set up remote syncing (cf. https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/dev_docs/local_setup/remote_clusters_ccr.md).
  2. Install a custom integration and a package from registry.
  3. Wait for the integrations sync task to complete.
  4. Check that only the package from registry was synced.

Checklist

@jillguyonnet jillguyonnet self-assigned this Oct 17, 2025
@jillguyonnet jillguyonnet added release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting Team:Fleet Team label for Observability Data Collection Fleet team labels Oct 17, 2025
@jillguyonnet jillguyonnet marked this pull request as ready for review October 17, 2025 14:00
@jillguyonnet jillguyonnet requested a review from a team as a code owner October 17, 2025 14:00
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Oct 17, 2025

Pinging @elastic/fleet (Team:Fleet)

nchaulet
nchaulet approved these changes Oct 17, 2025
View reviewed changes
Copy link
Copy Markdown
Member

@nchaulet nchaulet left a comment

Choose a reason for hiding this comment

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

code LGTM 🚀

@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Oct 17, 2025

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

✅ unchanged

cc @jillguyonnet

@jillguyonnet jillguyonnet merged commit 75d43bd into elastic:main Oct 17, 2025
21 checks passed
@jillguyonnet jillguyonnet deleted the fleet/228570-disallow-custom-integration-syncing branch October 17, 2025 19:16
@juliaElastic juliaElastic mentioned this pull request Oct 22, 2025
Closed
nickpeihl pushed a commit to nickpeihl/kibana that referenced this pull request Oct 23, 2025
@jillguyonnet @nickpeihl
[Fleet] Only sync integrations installed from registry (elastic#239567)
1773602 
## Summary

Closes elastic#228570

This PR limits integration syncing in Fleet to packages installed from
the registry. Other packages won't be picked up or shown in the sync
status.

To test:
1. Set up remote syncing (cf.
https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/dev_docs/local_setup/remote_clusters_ccr.md).
2. Install a custom integration and a package from registry.
3. Wait for the integrations sync task to complete.
4. Check that only the package from registry was synced.

### Checklist

- [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
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [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)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.
NicholasPeretti pushed a commit to NicholasPeretti/kibana that referenced this pull request Oct 27, 2025
@jillguyonnet @NicholasPeretti
[Fleet] Only sync integrations installed from registry (elastic#239567)
bababcd 
## Summary

Closes elastic#228570

This PR limits integration syncing in Fleet to packages installed from
the registry. Other packages won't be picked up or shown in the sync
status.

To test:
1. Set up remote syncing (cf.
https://github.com/elastic/kibana/blob/main/x-pack/platform/plugins/shared/fleet/dev_docs/local_setup/remote_clusters_ccr.md).
2. Install a custom integration and a package from registry.
3. Wait for the integrations sync task to complete.
4. Check that only the package from registry was synced.

### Checklist

- [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
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [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)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.
@jillguyonnet jillguyonnet mentioned this pull request Oct 28, 2025
Merged
3 tasks
jillguyonnet added a commit that referenced this pull request Oct 29, 2025
@jillguyonnet @elasticmachine
[Fleet] Allow syncing bundled integrations (#241011)
ccbc855 
## Summary

Closes #240925

#239567 limited remote
integrations sync to packages installed from registry. This PR adds
allowing bundled packages as well.

### Checklist

- [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)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
tkajtoch pushed a commit to tkajtoch/kibana that referenced this pull request Oct 29, 2025
@jillguyonnet @elasticmachine @tkajtoch
[Fleet] Allow syncing bundled integrations (elastic#241011)
d63b8b6 
## Summary

Closes elastic#240925

elastic#239567 limited remote
integrations sync to packages installed from registry. This PR adds
allowing bundled packages as well.

### Checklist

- [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)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
qn895 pushed a commit to qn895/kibana that referenced this pull request Oct 30, 2025
@jillguyonnet @elasticmachine @qn895
[Fleet] Allow syncing bundled integrations (elastic#241011)
1907723 
## Summary

Closes elastic#240925

elastic#239567 limited remote
integrations sync to packages installed from registry. This PR adds
allowing bundled packages as well.

### Checklist

- [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)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
ana-davydova pushed a commit to ana-davydova/kibana that referenced this pull request Nov 3, 2025
@jillguyonnet @elasticmachine @ana-davydova
[Fleet] Allow syncing bundled integrations (elastic#241011)
8ede3e3 
## Summary

Closes elastic#240925

elastic#239567 limited remote
integrations sync to packages installed from registry. This PR adds
allowing bundled packages as well.

### Checklist

- [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)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
albertoblaz pushed a commit to albertoblaz/kibana that referenced this pull request Nov 4, 2025
@jillguyonnet @elasticmachine @albertoblaz
[Fleet] Allow syncing bundled integrations (elastic#241011)
864b43f 
## Summary

Closes elastic#240925

elastic#239567 limited remote
integrations sync to packages installed from registry. This PR adds
allowing bundled packages as well.

### Checklist

- [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)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@nchaulet nchaulet nchaulet approved these changes

Assignees

@jillguyonnet jillguyonnet

Labels

backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Fleet Team label for Observability Data Collection Fleet team v9.3.0

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[Fleet]: Custom integration remains stuck in sync state for over 15 minutes under Integration syncing status flyout on uninstalling.

4 participants

@jillguyonnet @elasticmachine @nchaulet @kibanamachine