interactive add-cloud does not provide a default auth type

[Aaron Bentley]

According to requirements:
  System should provide a default auth type that is valid for the cloud type
  https://docs.google.com/document/d/1K2QPcdrsxAKpKEWT7RiRT-pL-D3LrLzl3QomVimKxAo/edit#

It does not do this. If I hit enter at the auth type prompt, it simply re-prompts.
$ juju add-cloud
Cloud Types
  maas
  manual
  openstack
  vsphere

Select cloud type: openstack

Enter a name for the cloud: j

Enter the API endpoint url for the cloud: j

Auth Types
  oauth1
  oauth2
  access-key
  userpass

Select one or more auth types separated by commas:

Select one or more auth types separated by commas:

Select one or more auth types separated by commas:

Select one or more auth types separated by commas:

Select one or more auth types separated by commas:

Select one or more auth types separated by commas:

[Nate Finch (natefinch)]

A default doesn't make any sense here. There's no "sane default", because there's no way for the system to know what's configured for that cloud.

[Aaron Bentley (abentley)]

The SRS doesn't demand a "sane" default, but it does demand a "default that is valid for the cloud type". This is entirely possible to provide. Even if it is a comma-separated list of all supported auth types, that would allow the user who has valid credentials to use them.

Rick has said that he wants the spec docs to be updated to reflect reality. As it stands, this behaviour does not meet the SRS requirements. If you believe the SRS requirement to be unattainable, please have the SRS doc updated before closing the bug.

[Ian Booth (wallyworld)]

Interactive add cloud can and should provide a valid list of auth types valid for the cloud. The user has first entered the cloud type and from there the valid auth types can be determined from the cloud type's credential schema

[Richard Harding (rharding)]

We should check on what's supported ootb with openstack in a canonical openstack install and start with that.

Manual/MAAS don't apply.

I'm not sure on what we need for vsphere and what the options are.

[Richard Harding (rharding)]

I've reached out to the OpenStack folks for experience on what the our typical OpenStack supports ootb. Putting this as incomplete until we get that feedback.

[Anastasia (anastasia-macmood)]

This has been fixed as part of ongoing improvements in the area.

In juju 2.1.0, we list available auth types for the selected cloud type.

For example, the output for openstack looks like this:

$ juju add-cloud
Cloud Types
  maas
  manual
  openstack
  vsphere

Select cloud type: openstack

Enter a name for your openstack cloud: <my cloud name>

Enter the API endpoint url for the cloud: <valid endpoint>

Auth Types
  access-key
  userpass

[Anastasia (anastasia-macmood)]

Comment #6 was an answer to listing valid auth type for selected cloud type questioned in comment # 3.

As for providing *sane* default, I agree with comment # 1 - the primary objective of interactive add-cloud is to help configure connection details for highly customisable clouds. There is no such thing as "default" auth type - it is highly subjective to how the cloud is setup. In fact, to provide a "default" would be confusing to the user as well as misleading if the option is selected by the user without a thought.

[Aaron Bentley (abentley)]

AFAICT, interactive add-cloud still does not provide a default auth type. It sounds more like "Won't Fix" than "Fix committed."

[Anastasia (anastasia-macmood)]

@Aaron
I'll bring it up with the team.
I still fail to see what "default" can be suggested unless it's just the first auth type in the list of all available ones. The whole idea of interactive add-cloud is so that the user tells us what their cloud is configured to use.

[Anastasia (anastasia-macmood)]

@Aaron,

After some deliberation, this is a Won't Fix as there is no way to determine what sane default auth type would be for custom clouds. We do not want to take a guess, make a suggestion and mislead the user.