Comment 2 for bug 1833879

I agree that commands that depend on the controller name shouldn't need to be passed the controller model. I don't think we have an intent to allow renaming the controller model at this time (either during bootstrap or at any other time). Having it be a field on the model definition might be an option (for things like 'list-controllers').

I'm not aware of any specific user feedback that says "I can't name my own model controller", so I don't think there is social pressure to update this. I can understand a desire to avoid a constant in our code that doesn't seem like it fits, but I would avoid going to great lengths for something that ends up YAGNI.