Comment 6 for bug 1836226

Currently preparations are being made to ensure that `--force` is not effective default.

The way that this currently works doesn't seem to make sense, I guess moving --force into add-unit would work, also I know it adds complexity but are there not different code paths for different clouds?

The reason I filed this bug was that when I was trying out the change, I moved onto another bug, forgot I built the profile on my local, then was faced with this situation.

Why does this profile get validated even when it's not being deployed? I may be missing some design decision or something, but again can't we just not deploy when the context is non-lxd?

If there's something I'm missing please feel free to correct me. I'm new. :-)