add-cloud command points to a deprecated option
Bug #1833629 reported by
james beedy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Anastasia | ||
2.6 |
Fix Released
|
Medium
|
Anastasia |
Bug Description
Using `juju add-cloud` I ran into a strange case where trying to re-add/replace a cloud that already exists in the local cache results in an endless loop experience.
https:/
Not really sure if this is just a messaging thing, workflow, or both.
Just wanted to note my experience.
Thanks!
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: add-cloud usability |
Changed in juju: | |
assignee: | nobody → Anastasia (anastasia-macmood) |
status: | Triaged → In Progress |
Changed in juju: | |
importance: | High → Medium |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Thank you, @james beedy,
I do not see a circular messaging. We do, however, consistently point you to a command version that we have deprecated. I'll update the message.