In some environments when the offering is set in config.yaml, the Quarkus CLI with set --stream not show support scope. When the --stream is removed from Quarkus CLI command the support scope is show without problem.

On QE environment, the RHEL have no problem, but windows show this bug. I have same problem on my machine, but my colleague don't have problem.

The affected machines:
quarkus ext list --support-scope --stream 3.27 not show any support scope e.g.

✬ quarkus-websockets WebSockets 3.27.0.redhat-00001 
✬ quarkus-websockets-client WebSockets Client 3.27.0.redhat-00001 
✬ quarkus-websockets-next WebSockets Next 3.27.0.redhat-00001

 
The quarkus ext list --support-scope show

✬ quarkus-websockets WebSockets 3.27.0.redhat-00001 deprecated
✬ quarkus-websockets-client WebSockets Client 3.27.0.redhat-00001 deprecated
✬ quarkus-websockets-next WebSockets Next 3.27.0.redhat-00001 supported

Using same commands on not affected machines the output is:

✬ quarkus-websockets WebSockets 3.27.0.redhat-00001 deprecated
✬ quarkus-websockets-client WebSockets Client 3.27.0.redhat-00001 deprecated
✬ quarkus-websockets-next WebSockets Next 3.27.0.redhat-00001 supported

There can be some problem in my environment, but this should be at least documented. As we encounter this in multiple environments and customers can have same problem.