`juju add-k8s` fails when prompting user for input
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Anastasia | ||
| 2.7 |
Fix Released
|
High
|
Anastasia | ||
Bug Description
Version: 2.7-rc2-disco-amd64
While doing some testing with microk8s and Juju, I added a new cloud called microk8s-test (I'm aware microk8s is a built-in cloud type, but I'm testing a specific use-case).
When I run this without the --client flag, I'm presented with a prompt but the command fails with ERROR EOF without giving me the chance to answer the prompt.
```
$ microk8s.config | juju add-k8s microk8s-test
This operation can be applied to both a copy on this client and to the one on a controller.
No current controller was detected but there are other controllers registered: use -c or --controller to specify a controller if needed.
Do you ONLY want to add k8s cloud microk8s-test to this client? (Y/n):
ERROR EOF
```
The command succeeds when run with the --client flag (or as-is with Juju 2.6.10)
| Changed in juju: | |
| milestone: | none → 2.7.1 |
| assignee: | nobody → Anastasia (anastasia-macmood) |
| importance: | Undecided → High |
| status: | New → Triaged |
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → In Progress |
| Changed in juju: | |
| milestone: | 2.7.1 → 2.8-beta1 |
| status: | In Progress → Fix Committed |
| Anastasia (anastasia-macmood) wrote | #2 |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
https:/