Incorporate auxillary information into API

[marcelstoer]

Is your feature request related to a problem? Please describe.
Feature request: the RHBQ information on https://endoflife.date/quarkus-framework is not available through the API at https://endoflife.date/api/quarkus-framework.json.

Describe the solution you'd like
I don't know how this could be structured best but it'd certainly be helpful if this information were available in the API. This would give https://github.com/hugovk/norwegianblue a chance to also render it.

Describe alternatives you've considered
Scraping the web UI 😜

Additional context
n/a

[welcome]

Thank you for opening your first issue here 👍. Be sure to follow the issue template if you chose one.

[captn3m0]

The RHBQ column comes from the extended Support field in the product YAML.

It is published in the API as extendedSupport, with the same semantics as the support/eol column (true/false/date). https://endoflife.date/api/quarkus-framework.json

We are working towards a v1 API in #2080 that should make more data accessible programmatically. (Feedback appreciated, here is the preview of the Quarkus API response).

[marcelstoer]

Thanks

[adriens]

BTW @captn3m0 , can you confirm me that the current API will not be dropped as soon as the v1 will be released ?

[captn3m0]

Yes, see discussion at #2066, and this discussion on the v1 PR where consensus is currently on 1 year of guarantee.

[adriens]

Yes, see discussion at #2066, and this discussion on the v1 PR where consensus is currently on 1 year of guarantee.

Great, so it will let me time to migrate data integration to the new API 👍