Clarification of Xfrout transfer_acl entries at different scopes

[Jeremy C. Reed]

On Sun, 5 Feb 2012, Michal 'vorner' Vaner wrote:

> On Sat, Feb 04, 2012 at 07:22:58PM +0000, Spain, Dr. Jeffry A. wrote:
> > > config show Xfrout/zone_config/transfer_acl
> > Xfrout/zone_config/transfer_acl[0]      {"action": "ACCEPT"}    any     (default)
> 
> I'm pretty sure this one does not exist. There must be a bug in the bindctl
> tool, it should have rejected this as the entry does not exist, but instead gave
> you a default for new entries in the zone_config list. I'll look if there's a
> ticket for this on Monday.

This was worked on in #1649 and merged 8 weeks ago:

> config show Xfrout/zone_config/transfer_acl
Error: zone_config is a list and needs an index

But:

> config add Xfrout/zone_config
> config show Xfrout/zone_config
Xfrout/zone_config[0]/origin    ""      string  (modified)
Xfrout/zone_config[0]/class     "IN"    string  (default)
Xfrout/zone_config[0]/transfer_acl/     list    (default)
> config show Xfrout/zone_config/transfer_acl
Error: zone_config is a list and needs an index
> config add Xfrout/zone_config
Error: {'origin': ''} already in /Xfrout/zone_config
> config add Xfrout/zone_config[1]             
Error: [{'origin': ''}] is not a map


This is still confusing. Can I have multiple zone_configs?