Today, an integration/policy template that includes a deployment_modes value in its manifest.yml as follows will appear in the integrations UI even if agentless is not supported:
This integration can't actually run in an environment that doesn't support agentless, so when agentless isn't supported/available this integration should be hidden from the UI at a minimum, and ideally installation should be prevented at the API level as well via a validation check in the POST /api/fleet/epm/packages API.
Today, an integration/policy template that includes a
deployment_modes
value in itsmanifest.yml
as follows will appear in the integrations UI even if agentless is not supported:This integration can't actually run in an environment that doesn't support agentless, so when agentless isn't supported/available this integration should be hidden from the UI at a minimum, and ideally installation should be prevented at the API level as well via a validation check in the
POST /api/fleet/epm/packages
API.