-
Notifications
You must be signed in to change notification settings - Fork 5
feat(asset): add asset categorization support #298
Copy link
Copy link
Labels
featureType: new feature or capability (feat:).Type: new feature or capability (feat:).needs triageNeeds triage from the Filigran product team.Needs triage from the Filigran product team.solvedResolved (should be linked to the solving PR).Resolved (should be linked to the solving PR).
Description
Activity
Metadata
Metadata
Assignees
Labels
featureType: new feature or capability (feat:).Type: new feature or capability (feat:).needs triageNeeds triage from the Filigran product team.Needs triage from the Filigran product team.solvedResolved (should be linked to the solving PR).Resolved (should be linked to the solving PR).
Summary
Add the canonical two-level asset taxonomy to pyoaev so producers (collectors, custom integrations) can classify endpoints with the new categorization fields introduced in OpenAEV, instead of free-form strings.
Changes
pyoaev.asset_typesmodule exposingAssetCategory,AssetSubCategory,CloudProviderandAssetCriticalityasstrenums, exported from the package root.EndpointManager: makeendpoint_platform/endpoint_arch(andendpoint_hostname) optional withasset_nameas the only required attribute, and add the optional categorization / cloud fields (asset_category,asset_subcategory,asset_criticality,asset_internet_facing,asset_cloud_provider,asset_cloud_native_type,asset_cloud_region,asset_metadata,endpoint_url).Context
Dependency of OpenAEV-Platform/openaev#6452 (asset categorization). The SDK enums mirror the backend taxonomy so producers send backend-aligned values on the wire.