Fallback to the default platform catalog if available registries do not provide any catalog #21339
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently we are falling back to the default platform catalog (or suggesting user to do that manually) when we find that none of the configured registries is available.
However, today we had a case when the registry was returning its descriptor, indicating that it's available, but was failing to resolve the catalog artifacts. That would still be equivalent of the registry not being available, in which case we should also either fallback or suggest a workaround.
This change is adjusting the
quarkus:create
goal to fallback to the default platform if that happens.