Bug HUB CLI missing modules

After updating to the 2.4.0 hub version we noticed that our automated builds started to fail installing the modules listed in the "C:\Program Files\Unity\Hub\Editor\<Verson>\modules.json" manifest file correctly.

We noticed that there's also missing modules that used to exist, for example:
universal-windows-platform is no longer listed in the --headless help
windows-il2cpp was renamed to just windows, which fails to match the modules.json list

What we expected is the list of modules available to install in the CLI matched the ids of the modules listed in the editor's module.json

Our question for Unity:
Has the uwp module support been bundled together with windows?
Are there plans to better support breaking changes like this in the future when renaming or removing modules?
Can we ensure that the list of modules in the editor's module.json file is available as an installable module for the CLI?

Opened case 1279552

 

I am also having this same issue with our CI build script.

 

A bit more information on this. It seems the 2.4.1 update fixed the individual module id usage, but we've also narrowed it down to multiple modules being defined in the CLI command failing.

Pre 2.3 this worked but now fails:

Code (csharp):

1. "Unity Hub.exe" -- --headless im -v 2020.1.8f1 -m windows-il2cpp -m universal-windows-platform

We opened a new ticket for this specifically: Case 1284906

 

Just tested with Hub 2.4.2. Seems to have the same issue described in this thread.

Still unable to install more than one module at a time using the install-module argument with any number of module arguments:

"Unity Hub.exe" -- --headless im -v 2020.1.14f1 -m android -cm -m webgl

 

Thank you so much for the details regarding Unity Hub CLI, I’ve gone ahead and documented the conversation and shared it with the team. Kindly note that there will be upcoming documentation for this.