I understand what you’re saying but there is nothing clean and smooth about this sentiment (IMO). Minor configuration changes, like IP addressing and VLAN assignments, are common and should not require someone to completely redeploy a machine in order for MAAS to reflect the ground truth of a system.
I really like MAAS, and I’m a big believer in open source, but I’m left feeling the same frustration as @mrdmn by the lock-in that MAAS forces upon you.
For me specifically, I had a machine that I depended heavily upon on my home network. I was unaware that this machine’s network configuration had changed to “unconfigured” at some point. Once that happened, I’m left trying to get the machine’s network configuration to be the same as before. On the machine itself, its fairly trivial thru netplan configs. However, I’m depending on MAAS for DHCP and DNS. Which leads me full circle back to the MAAS lock-in. You can’t just alter the MAAS bind and dhcp config files. There is heavy reliance on MAAS’s backend database for IP addressing. I tried poking around the database, and even making changes to it, but I quickly found that it wasn’t helping because I wasn’t triggering all the backend scripts to keep MAAS happy and congruent.
I ended up having to set the IP address statically on the machine, and statically in MAAS just to get things back to semi normal.