Comment 1 for bug 1508746

I'm not convinced we need another code change for this. Since this is for a dev/test use case, can't you just automate this with a script to call the API?

It would be possible to have an option to customize the filtering. But it would be likely that by the time "apt-get install" is finished and the default cluster registers with the region, it's too late to modify a special setting for this. (Unless no interfaces are being added at all; that's the only time re-registering causes any changes.)

I think the real solution to this is to separate state from configuration in the database. That is, when the state of the cluster interfaces is discovered and presented to MAAS, nothing should be configured (and thus become "configuration" rather than "state") until the user approves it. Right now, discovered interfaces are entered *directly* into the configuration, and *that* is the root cause of this bug. (you could compare this to, if you install BIND for the first time, if the first time you ran the daemon it suddenly decided to rewrite a bunch of your configuration files in /etc - that would be just plain wrong!)