Right now it appears that if a single table matches multiple regexes, the effects from the first regex will be applied, and then the effects of the second one will be applied immediately afterward, and so on. This can lead to some very silly things, such as increasing the provisioning of a table and then immediately reducing it again.
Since we probably don't want to change the semantics of people's existing configs, I'm thinking the best thing to do here is make it emit loud warnings (but not fail) when it detects that a table matches two regexes. Once you know that the problem exists, it's always possible to write ugly regexes such that each table matches at most one.
Now printing a warning if a table/gsi matches multiple regexps #203
Ok, this is not like Shell Shock, but I'm still a bit shocked :)
I could reproduce it and I agree that it's not optimal to fix it. I have now released 1.18.5 which addresses this issue.
And thanks for the report!