I was just wondering if you could help me with something and whether this is the intended behaviour of Curator or not... I am currently setting up a number of automated alias actions in Curator, for things like "today", "yesterday", "last 7 days" etc etc and have come across an odd potential issue...
When testing my "Last 7 Days" function, it is set up as the following:
action: alias description: >- Add relevant event indexes to a "Last 7 Days" alias for rapid searching etc options: name: events_last_7 extra_settings: timeout_override: ignore_empty_list: True continue_if_exception: False disable_action: False add: filters: - filtertype: pattern kind: prefix value: event- exclude: - filtertype: age source: name direction: younger timestring: '%Y.%m.%d' unit: days unit_count: 7 exclude: remove: filters: - filtertype: pattern kind: prefix value: event- exclude: - filtertype: age source: name direction: younger timestring: '%Y.%m.%d' unit: days unit_count: 7 exclude: True
The problem I am having is, if I comment out the
remove section it works fine (I only have 4 indexes as I'm testing which are dated over the last 4 days) but if I put the remove section in - because there are no indexes older than 7 days, it seems to return an empty list and fail the whole action?
I would expect the
add action to complete successfully and the
remove one to do nothing - or does it simply see the whole lot as one
action which fails if one element of it fails?