Comment 6 for bug 1730747

No it isn't. We implemented functionality for users to massage space names and network topology, along with a slew of safety checks based on endpoint bindings and space constraints.

What would be required here is to extract those checks into a general-use module and apply them to the reload-spaces logic so that if safe, we just consume detected MAAS space/subnet mutations.

At present this functionality remains largely as first conceived, which prevents most changes. The exception is this patch from Simon that introduced the ability to delete spaces that were removed in MAAS.