Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API to get multiple product with cycles mapped to them #5191

Open
Vasanth2896 opened this issue May 27, 2024 · 7 comments
Open

API to get multiple product with cycles mapped to them #5191

Vasanth2896 opened this issue May 27, 2024 · 7 comments
Labels
api Changes that relates to API enhancement New feature or request

Comments

@Vasanth2896
Copy link

Hi,

I wish to have a API which is GET request to get multiple products with their cycles

For Eg:

product: {"python":"3.12","ansible-core":"2.17"}

Something like this

@Vasanth2896 Vasanth2896 added the enhancement New feature or request label May 27, 2024
Copy link

welcome bot commented May 27, 2024

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

@captn3m0 captn3m0 added the api Changes that relates to API label May 28, 2024
@captn3m0
Copy link
Member

While this might be doable, can you provide a use-case for such an API?

@Vasanth2896
Copy link
Author

Vasanth2896 commented May 28, 2024 via email

@nicpenning
Copy link

Looking at a SIEM use case where endoflife.date data can be correlated with product information from vulnerability scanners, EDR solutions, and other log sources that live in a central location would be ideal.

I would be interested in an API endpoint that provides all product information with all eol information.

This would allow for SIEM queries to match on endoflife products and alert security analysts or visualize via dashboards what software is end of life in the environment. This would be another source of this as vulnerability scanners do contain some of this information but this would further validate or identify others.

The current API endpoints are too limiting to simply ingest them as a source for collation in a SIEM. Having just 1 API call to have all of the data that can be checked against every 24 hours (or as needed) would make this an easy source for correlation. Otherwise, more advanced queries are needed to target the product, then get the details for that product. Currently the body details of the request also do not contain the product itself which might be another FR on it's own if an endpoint does not provide all details for all products to something like this (Ubuntu example):

[
  {
    "cycle": "21.04",
    "lts": false,
    "releaseDate": "2021-04-22",
    "support": "2022-01-01",
    "eol": "2022-01-01",
    "latest": "21.04",
    "link": "https://wiki.ubuntu.com/HirsuteHippo/ReleaseNotes/",
    "product" : "ubuntu"
  },
  {
    "cycle": "20.10",
    "lts": false,
    "releaseDate": "2020-10-22",
    "support": "2021-07-07",
    "eol": "2021-07-07",
    "latest": "20.10",
    "link": "https://wiki.ubuntu.com/GroovyGorilla/ReleaseNotes/",
    "product" : "ubuntu"
  }
]

@captn3m0
Copy link
Member

captn3m0 commented Jul 3, 2024

Would a Prometheus exporter work for you?

#975

@nicpenning
Copy link

Not for me it seems. I am looking for direct and simple APIs to reveal this info.

@captn3m0
Copy link
Member

captn3m0 commented Jul 3, 2024

We have a full product data API in the upcoming v1 of the API: https://deploy-preview-2080--endoflife-date.netlify.app/api/v1/products/full/

Documented at https://deploy-preview-2080--endoflife-date.netlify.app/docs/api/v1/

This might have some stale data, but we're getting closer to taking this live. Feedback is appreciated at #2080.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Changes that relates to API enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants