Skip to content

Migrate to new Azul metadata API (from Zulu Discovery API) #795

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

Open
StefMa opened this issue Apr 14, 2025 · 1 comment
Open

Migrate to new Azul metadata API (from Zulu Discovery API) #795

StefMa opened this issue Apr 14, 2025 · 1 comment
Labels
feature request New feature or request to improve the current logic

Comments

@StefMa
Copy link

StefMa commented Apr 14, 2025

Description:
As of today, you're using the Zulu Discover API to fetch available jdks from there:

const availableVersionsUrl = `https://api.azul.com/zulu/download/community/v1.0/bundles/?${requestArguments}`;

According to this documentation, the new Metadata API gets promoted in favor of the old Discovery API.

This change were already announced in the beginning of 2023.

I"m not a zulu employee or something, but I guess it make sense to migrate to the new metadata api before they sunset (if its planned 🤷 ) the old Discovery API.

I just want to make you aware of it as I just found it 🙃

Are you willing to submit a PR?

Not yet

@StefMa StefMa added feature request New feature or request to improve the current logic needs triage labels Apr 14, 2025
@priya-kinthali
Copy link

Hello @StefMa👋,
Thank you for this feature request. We will investigate it and get back to you as soon as we have some feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request to improve the current logic
Projects
None yet
Development

No branches or pull requests

2 participants