Allow specifying model name in headless

[marcoceppi]

We're using something like the following in headless:

conjure-up kubernetes-core localhost my-controller
conjure-up kubernetes-core localhost my-controller

But this creates model names that don't represent what the deployment is. Suggestion to allow a third positional argument to set model name:

conjure-up kubernetes-core localhost my-controller prod-test
conjure-up kubernetes-core localhost my-controller qa-cluster

Alternatively, it might be interesting to implicitly set the model name in the UI above the deploy screen as a prefilled but editable "Deployment name" to expose this functionality in the UI. I'm hesitant to put it there, choice fatigue, etc.

[mikemccracken]

I think the main concern here might have already been addressed by the changes in #619 , right?

The problem @marcoceppi pointed out was "model names that don't represent what the deployment is", and while allowing the user to set them is one way to fix that, isn't automatically generating meaningful names solving the same problem without requiring the user to do more?

[battlemidget]

I think @marcoceppi was more concerned with providing his own names for the models to represent the different phases of the application(s) deployed.

[battlemidget]

We decided to stick with the recent changes that name the controllers/models relevant to whats being deployed.

[marcoceppi]

Doesn't resolve this bug.

…

On Wed, Feb 8, 2017, 12:32 Adam Stokes ***@***.***> wrote: We decided to stick with the recent changes that name the controllers/models relevant to whats being deployed. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#635 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAET1d0h5nO_zRLGcg2KN43c68w3KVr4ks5rafvogaJpZM4LxfqG> .

[mikemccracken]

@marcoceppi can you elaborate? I thought it solved your problem.

[marcoceppi]

I would like to name my models in headless. Repeating 2 kubernetes core deployments, let alone 5, mean I have models that are names conjure-up-kubernetes-core-xxxx which is meaningless for me.

…

On Wed, Feb 8, 2017, 15:09 Michael McCracken ***@***.***> wrote: Reopened #635 <#635>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#635 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAET1RE_1eMVSZ1XAVLcNAc_KWrHum9Kks5raiCvgaJpZM4LxfqG> .

[mikemccracken]

ok, thanks for clarifying On Wed, Feb 8, 2017 at 12:10 PM, Marco Ceppi <notifications@github.com> wrote:

…

I would like to name my models in headless. Repeating 2 kubernetes core deployments, let alone 5, mean I have models that are names conjure-up-kubernetes-core-xxxx which is meaningless for me. On Wed, Feb 8, 2017, 15:09 Michael McCracken ***@***.***> wrote: > Reopened #635 <#635>. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#635 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe- auth/AAET1RE_1eMVSZ1XAVLcNAc_KWrHum9Kks5raiCvgaJpZM4LxfqG> > . > — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#635 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABr6qrDd-D6jseQvHTNJpk-ezu2Bfo9Vks5raiFSgaJpZM4LxfqG> .

[marcoceppi]

Documentation would need to be updated, but thank you!