This feature allows users to pre-configure devices by specifying desired configurations that are automatically applied when a ResourceChanged event occurs. The newly introduced snippet service is responsible for managing this process.
- ☑ Device Configuration: Users can create and store configurations for devices. These configurations are automatically applied when a
ResourceChanged event occurs. - ☑ Event-Driven Configuration: The configuration is triggered by the
ResourceChanged event. Users can set filters to define the conditions under which configurations are applied. - ☑ Filter Conditions: Users must set at least one of the following filters: DeviceID filter (trigger based on specific device IDs), Resource-Type filter (trigger when all specified resource types are present), href filter (trigger based on specific href values). All specified filters must be met for the configuration to be applied. For DeviceID and href filters, any listed value can trigger the filter. For the Resource-Type filter, all listed values must be present.
- ☑ Optional JQ Expression: Users can optionally use a JQ expression to filter the content of the
ResourceChanged event. The JQ expression must evaluate to true for the configuration to be applied. - ☑ User Interface: A user-friendly UI is provided to manage configurations and set filters easily.
- ☑ APIs: The snippet service provides both a gRPC API and an HTTP API, allowing users to interact with the service and perform configuration-related operations.
- ☐ Enhanced Filtering Mechanisms: Additional filter conditions and more complex filtering logic will be supported to offer even greater flexibility and control over configuration application.
- ☐ Apply Configuration to Different Devices: Users will be able to apply configurations to devices other than the one that triggered the
ResourceChanged event.
