I had to read your comment a few times but I still don't see how it explains what Sandor and I have observed: that `bootstrap --constraints` only applies to the 'controller' and 'default' models.
I've never heard the term "application constraint" but what I think you mean is that it's a constraint that is not inherited from a model. The `add-machine` command does not fit in to this definition.
In lieu of getting rid of `bootstrap --constraints` entirely I agree that renaming the option is an improvement. The problem with `--model-constraints` is that it suggests that it applies to a specific model, or even that it applies to every model (present and future), which it does not.
I had to read your comment a few times but I still don't see how it explains what Sandor and I have observed: that `bootstrap --constraints` only applies to the 'controller' and 'default' models.
I've never heard the term "application constraint" but what I think you mean is that it's a constraint that is not inherited from a model. The `add-machine` command does not fit in to this definition.
In lieu of getting rid of `bootstrap --constraints` entirely I agree that renaming the option is an improvement. The problem with `--model- constraints` is that it suggests that it applies to a specific model, or even that it applies to every model (present and future), which it does not.
Let's talk offline.