You can go around this in Curator with the
This option was added expressly for the cases where you want Curator to continue even if no indices were in a list. This separation had to be made from the regular
continue_if_exception which catches all other kinds of exceptions. However, the truth is, to Curator, an empty list condition is an error. It cannot proceed without the
ignore_empty_list option. There is no way to suppress this message, or change it to not be an error.
A dry_run needs to show the user exactly what will happen with a dry run. The disparity comes from the fact that the dry_run does its own iteration over the values, separate from the regular action. They do not share the same code
The allocate action does still log what's happening when it does the action, but the appearance is different from the dry_run output because it is applying the settings in a batch, rather than index by index.