juju list-controllers --format yaml to include provider type and properties

Adam, to better understand your requirements, can you please answer a couple of questions?

1. Is there a reason why you can't just use "juju get-model-config" to get the type? And MAAS server address?
2. If you need to be able to get this information without making API calls, do you need to get this information from any machine other than the one that ran the bootstrap command?

I'm working on a change that adds "bootstrap config" to the output of show-controller. This will only be available on the client that ran "juju bootstrap". Bootstrap config includes:
 - the cloud name (e.g. aws)
 - the cloud type (e.g. ec2)
 - the region name (e.g. us-east-1)
 - any additional config passed to bootstrap with --config

Would that work for you?

Adam, please see my proposed change here: https://github.com/juju/juju/pull/4864. Sample abridged output:

local.ctrl:
  details:
    ...
  accounts:
    ...
  current-account: admin@local
  bootstrap-config:
    config:
      name: admin
      type: lxd
    cloud: lxd
    region: localhost

Here's a more useful example, for AWS:

bootstrap-config:
  config:
    name: admin
    type: ec2
  cloud: aws
  region: ap-southeast-2
  endpoint: https://ap-southeast-2.aws.amazon.com/v1.2/
  credential: axw

Responding inline:

Adam, to better understand your requirements, can you please answer a couple of questions?

1. Is there a reason why you can't just use "juju get-model-config" to get the type? And MAAS server address?

>> I'm not sure, I haven't looked at this particular command.

2. If you need to be able to get this information without making API calls, do you need to get this information from any machine other than the one that ran the bootstrap command?

>> Probably not from any machine though I guess I could see where getting this information from another user/system that didn't run the bootstrap command.

I'm working on a change that adds "bootstrap config" to the output of show-controller. This will only be available on the client that ran "juju bootstrap". Bootstrap config includes:
 - the cloud name (e.g. aws)
 - the cloud type (e.g. ec2)
 - the region name (e.g. us-east-1)
 - any additional config passed to bootstrap with --config

Would that work for you?

>> Yea this would work for my current needs (I'm not sure what to expect beyond this from a user's perspective)

Re "juju get-model-config": that's the new name for "juju get-env".

You can do "juju get-model-config type" to get the current model's type; and then "juju get-model-config maas-server" to get the MAAS server endpoint.

I've improved the output for bootstrap-config a bit based on a suggestion by Ian, and I'm going to commit it. If there's a need to get the cloud type from another client, without going over the API, then we'll address that separately.

Marking this as fixed for beta-3. Please take a look when it's out, and let us know if there's anything else you need.