Comment 2 for bug 1768308

Thanks. I will open a bug for fixing the help. Currently it shows:

If '--constraints' is used, its values will be set as the default
constraints for all future workload machines in the model, exactly as if
the constraints were set with `juju set-model-constraints`.

Having two options that affect the same object is counterintuitive, especially since the help does not mention the aspect of precedence (i.e. '--bootstrap-constraints' overrides '--constraints').

Do the individual constraints override the other or do all the constraints given by --bootstrap-constraints get preferred?