Recipe-type validator configuration via UI
This release introduces new features for configuring recipe-type validators via the UI, extends the Management API with new endpoints and filter options, improves the scoping for selecting IoT Rollouts entities, and fixes several bugs related to recipe imports and creation.
New features
Recipe-type validator configuration using the UI
- ROLEX-2104: Allow configuring the
metadata
validator using the UI. - ROLEX-2072: Allow configuring the
artifact size
validator using the UI. - ROLEX-2072: Allow configuring the
distribution set assignment
validator using the UI.
Management API extensions
- ROLEX-2072: Extend the
system-types
API with an endpoint to provide a list of compatible software module types for a given system type. - ROLEX-2078: Introduce
reported after
andreported before
filter options for system actions in both the API and UI, allowing users to filter system actions by a specific timeframe.
Improvements
- ROLEX-2094: Allow uploading signatures in every recipe state except
DRAFT
.
Better scoping when selecting IoT Rollouts entities
- ROLEX-2137: Scope
system distribution set
creation in the API and UI, allowing only the selection of compatible distribution sets. - ROLEX-2072: Scope excluded software module types selection for the
artifact size
validator in the API and UI, allowing only the selection of compatible software module types.
Bugs fixed
- ROLEX-2103: Fix the issue where importing recipes with a missing recipe type does not open the selection dialog.
- ROLEX-2115: Fix the issue where importing recipes with distribution set type, name, and version does not assign the distribution set.
- ROLEX-2116: Fix the issue where creating multiple recipes at once referencing the same tag leads to an internal server error.