Option to disable "registry.quarkus.io"

[thibaultmeyer]

Describe the bug

My company has a strict proxy policy, so we got lot of errors with the DEV UI and Quarkus Ext. Registry.

Is it possible to disable it ?

Caused by: java.lang.RuntimeException: Failed to initialize the Quarkus Maven extension manager
	at io.quarkus.devtools.project.QuarkusProjectHelper.getCachedProject(QuarkusProjectHelper.java:61)
	at io.quarkus.devui.deployment.menu.ExtensionsProcessor.getQuarkusProject(ExtensionsProcessor.java:209)
	at io.quarkus.devui.deployment.menu.ExtensionsProcessor.lambda$getInstalledNamespaces$4(ExtensionsProcessor.java:123)
	at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
	... 6 more
Caused by: io.quarkus.registry.RegistryResolutionException: Failed to resolve the Quarkus extension registry descriptor of registry.quarkus.io from registry.quarkus.io (https://registry.quarkus.io/maven)
	at io.quarkus.registry.client.maven.MavenRegistryClientFactory.buildRegistryClient(MavenRegistryClientFactory.java:101)
	at io.quarkus.registry.ExtensionCatalogResolver$Builder.buildRegistryClients(ExtensionCatalogResolver.java:120)
	at io.quarkus.registry.ExtensionCatalogResolver$Builder.build(ExtensionCatalogResolver.java:89)
	at io.quarkus.devtools.project.QuarkusProjectHelper.getCatalogResolver(QuarkusProjectHelper.java:195)
	at io.quarkus.devtools.project.buildfile.MavenProjectBuildFile.getProject(MavenProjectBuildFile.java:75)
	at io.quarkus.devtools.project.buildfile.MavenProjectBuildFile.getProject(MavenProjectBuildFile.java:66)
	at io.quarkus.devtools.project.QuarkusProjectHelper.getCachedProject(QuarkusProjectHelper.java:59)

Expected behavior

An option to disable Quarkus Registry Extension in Dev UI

Actual behavior

Lot of exceptions

Output of java -version

graalvm-ce-21.0.2

Quarkus version or git rev

3.19.4 / 3.20.0

Build tool (ie. output of mvnw --version or gradlew --version)

Maven 3.9.9

[gsmet]

@aloubyansky @phillip-kruger I wonder if we should avoid resolving the extension catalog when loading the UI?

That being said, there are probably a lot of things you can't do with the Maven plugin or the CLI if you don't have the extension catalog.

@thibaultmeyer when you say you have a strict proxy policy, does it mean that:

• you absolutely do not want to proxy registry.quarkus.io so that everything works OOB?
• you would like to but Quarkus doesn't respect your proxy settings?

[thibaultmeyer]

@gsmet

Yes, I'd like everything to work ‘out of the box’. In terms of ideas, I had in mind :

• A simple option to deactivate this functionality (in the application.conf, would be nice)

or

• Leave it as it is now, but less intrusive:
  • don't retry every time the page is displayed
  • hide the stacktrace on console, just print a WARN log
  • don't display the big red error banner.
  • In this case, the + button on DevUI could display a message like ‘This functionality is not available because the registry could not be reached’.

[aloubyansky]

I think it's reasonable request. Project management capabilities are relatively expensive (even to initialize), so having a switch could be a good idea.
We already have .quarkus/config.yaml that could potentially be used as a config source. This file could be under user home and/or project directory.
@phillip-kruger wdyt?

[phillip-kruger]

Yea that should be added. I can add it to the normal config or @aloubyansky if you have some documentation how to get values from system wide setting I can get it from there.