`juju register` should add cloud definition to local client config

[jamesbeedy]

@rick_h

Fair enough but you did originally point out "The user can not add their own model until they have a cloud + credential definition for the cloud " so I’m just stating that I’m not comfortable going with credential definitions. I also think that we have to worry about things like collisions in folks that do already have a cloud definition as well.

+1 to all this. After thinking about it, I guess going through the add-cloud interactive prompt isn’t too cumbersome, and only takes a user to know a few minimum configs for their cloud. We just hit some bumps yesterday trying to get users registered and working on our openstack controller and I was trying to touch on some of the papercuts and pain points we hit.

@rick_h

This starts to feel like perhaps we can do something with an interactive register command that gives an option to copy locally or what not as optional steps, but doesn’t require it for things like scripted setups, or setups where you really don’t want the clients to have more than they need to get the job done.

Totally - then we wouldn’t be making any assumptions about how the cloud would be configured, but also give the user the option to have the cloud definition automatically added if they choose. I think I’m starting to see how automatically adding things to the cloud definition may not be as simple as I initially thought. That said, I like the where you are going with this!