`juju offers` should not give an error when there are inaccessible offers
Bug #1754748 reported by
james beedy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
When a user runs `juju offers` on a model for which they are not granted permissions on the endpoint they get a cryptic and broken feeling message.
$ juju offers --debug | https:/
Can we get a more consumable and understandable error message here that directs the user to the next step please instead of just broken juju.
thx
To post a comment you must log in.
Is the issue that there is an offer in bdx/daniel-redis, but they shouldn't even have visibility on it (much less getting a NotFound error).
Or is the client currently switched to a model that they don't have access to?