Following config will break routing: {"type":"table", "table": "main"}

{"type": "rule"} has an optional parameter "table". The value could be "main" as a fallback for a more generic rule (ie. from net1 to net1) via a specific table (ie. SF2). If {"type": "table"} does not exist for the selected table in the rule definition, the charm will raise an exception stating that the table is missing.

advanced-routing-config parameter now accepts:
{"type": "table", "table": "main"}

However, the "main" table is the default for rules that don't specify a table, and the charm will flush and delete the "main" table if the above {"type": "table"} definition (for the main table) exists.

Validation is needed to avoid:
{"type": "table", "table": "main"}