[EPM] Package installed by upload with no equivalent in the registry not shown #86268
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:EPM
Fleet team's Elastic Package Manager (aka Integrations) project
Team:Fleet
Team label for Observability Data Collection Fleet team
Current situation:
When a package has been installed by direct upload, and no package by the same name exists in the registry, the package is not shown on the list of installed integrations, and it is not available to be added to a policy.
Proposed change:
All installed packages should appear in the list of installed integrations, regardless of installation source, and be available to be added to a policy.
The text was updated successfully, but these errors were encountered: