search

quarkusio / registry.quarkus.io

Quarkus Extension Registry application
https://registry.quarkus.io
Apache License 2.0
10 stars 11 forks source link

Feature request: Endpoint to get the extensions, in a given stream #179

Open holly-cummins opened 1 year ago

holly-cummins commented 1 year ago

I've been a bit puzzled how to find the contents of a given platform. https://registry.quarkus.io/q/swagger-ui/#/Client/get_client_platforms gives me a list of streams and boms, but parsing the boms myself didn't look like much fun. @aloubyansky points out this capability is present in the Java API, but missing in the REST API. Hopefully it will be a quick addition.

The goal would be to query the registry, passing in a stream, and get back the extensions in that stream.

aloubyansky commented 1 year ago

@holly-cummins would you like to limit the extensions to the platform origin or also include extensions from quarkiverse that are compatible with the requested platform stream (i.e. the recommended quarkus version from that stream)?

holly-cummins commented 1 year ago

@holly-cummins would you like to limit the extensions to the platform origin or also include extensions from quarkiverse that are compatible with the requested platform stream (i.e. the recommended quarkus version from that stream)?

Yes. :)

Could we have two endpoints, or a query parameter to set how much we include? (Greedy!) I'd assumed it would just be the extensions in the platform origin, and that seems most logical to me if I call something like /client/platforms. However, for my particular use case, having the list of everything that's compatible would be even more useful, and allow me to solve some other problems.

I don't need both at once, though, just one of the two would be great.