It is hard to open juju API if you're not implementing a ModelCommand

[Roger Peppe]

Much of the logic for finding out the current model and controller
lives in ModelCommandBase.SetModelName and related
methods.

When implementing a command that is not a ModelCommand
(for whatever reason - perhaps it's a regular Go command that
isn't using the juju/cmd package), connecting to the API
of the current model involves a lot of copy and paste
of the code in ModelCommandBase and friends.

There should be a high level package API that makes
it trivial to connect to the Juju network API.

[Anastasia (anastasia-macmood)]

Since this bug was filed, there was a new command base introduced - juju/cmd/modelcmd.ControllerCommand.

I believe this base allows to achieve what you described, so I believe this is fixed.

Let me know if you think otherwise.

[Simon Richardson (simonrichardson)]

I'm reopening this one.

It really is way too hard to open an API connection to connect to Juju without using the cmd package. You shouldn't rely on anything in the cmd package to open an API connection.

An example of what is actually required can be found here[1], yet somehow we still have modelcmd in the mix. This really should never be the case.

If we want others to play nicely with Juju, we should fix this with some expediency.

1. https://github.com/SimonRichardson/juju-api-example/tree/main/client

[Canonical Juju QA Bot (juju-qa-bot)]

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.