also respect a
and vise-a-versa. I say this because we are not consistent with using one or another.)
. Although at the same time, given that the enable flags for events are growing in number, we could just have a flag with a list of table names to enable, instead of a one flag per table. Then we can maybe keep one flag per feature of a single table. Like maybe a table can get multiple events type, and you want to enable only some.
", yes but we would want to handle backwards compatibility for existing configurations/flagfiles/etc that use the existing
versions. I am thinking generically for all of these types of flags in the tool.