[UX] juju add-cloud should use the cloud name provided in the config file

Bug #1622606 reported by Chris Glass on 2016-09-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
Medium
Unassigned

Bug Description

When adding a cloud to juju via the "add-cloud" command, if the name given as an argument differs from the name passed in the file (if the file has a single cloud), juju complains

ERROR cloud "<name>" not found in file "config.json"

Since the config file contains only a single cloud, it would be nice from a UX perspective to:

- Make the cloud name optional in the CLI (use the one from the file)
- If the cloud name is provided by the user, ignore the one in the config file and use whatever the user gave.

Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
Changed in juju:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 2.1.0
tags: added: usability
no longer affects: juju-core
Curtis Hovey (sinzui) on 2017-02-17
Changed in juju:
milestone: 2.1-rc2 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers