Unlike the web interface this command doesn't "discover" and return a list - it just blindly installs anything it finds which is bad as the expectation is that it would be like the web interface.

Possibly consider breaking this up into two commands, one for discovering and one for installing, maybe even with a --installall param on the discover command to blindly install all it finds.

Just thoughts

Unlike the web interface this command doesn't "discover" and return a list - it just blindly installs anything it finds which is bad as the expectation is that it would be like the web interface.

I thought we had this discussion before?

nothing found https://github.com/joomla/joomla-cms/issues?q=is%3Aissue+CLI+author%3APhilETaylor+is%3Aclosed but I would not be surprised.

#31524 (comment)

Does this find the extensions or does it install them?

Well that's the point. It does both, blindly installing anything it finds. My point is that is not really what we (Joomla) should be looking to do and that the command should be broken up or improved,

If you want to install an extension specifically, then you can give the id. Then only this one will be installed.

but how do you find out which ones are available?

Its still a totally different expectation to the admin console.

There should be a

"Discover" = "List of discovered extensions"
"install All" = "installs all discovered extensions"
"install a single extension" = "installs a single discovered extension"

The last two can be merged with input options/arguments I guess

At the moment the default is just to discover and install all. I say that's the wrong expectation. Just running the command should give a LIST of discovered extensions, else where am I to get the ID from to install...

But all this is all mute anyway, because it doesn't EVEN WORK - it doesn't discover anything at the CLI !!!

Here you can see what I had to do to find, discover and install the extensions before I setup Joomla in DPDocker. Perhaps it helps.

please test #33749