write privileges should not be required to see model machine info
Bug #1660745 reported by
Roger Peppe
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
Bug Description
The ModelInfo API call only returns information about machines if
you have write access. This is an odd restriction, especially
as FullStatus returns information about machines even if you
only have read-only access.
IMO the write privilege requirement should be restricted to operations that
actually perform modification operations its meaning is intuitive. Arbitrary
restrictions like this muddy the semantics and make Juju harder to
reason about.
For background, see http://
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: usability |
| tags: | added: eda |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
It seems to be an oversight. We agree that read-access should be sufficient.