-
Notifications
You must be signed in to change notification settings - Fork 20
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
releases: Consider using new Releases API instead of Checkpoint #9
Comments
New API is now live and docs are available at https://releases.hashicorp.com/docs/api/v1/ |
I think we could try to move However I'd like to explore the possibility of the API exposing version constraint resolution endpoint, so that we don't have to keep looping over all versions to pick just one. |
Hi, has there been any more discussions on how you'd like to implement the API? I'd like to contribute towards some of that work. |
@jukie Not yet, but we did discuss a potential addition of a new endpoint to the API, ideally prior to the implementation. Specifically one that would allow us to resolve product version based on constraint, i.e. something similar to https://releases.hashicorp.com/docs/api/v1/#operation/getReleaseV1 where one can pass constraint such as This would allow us to more easily/efficiently re-implement Currently the querying is pretty inefficient in that we have to pull all versions and range over every single one until we find the one that matches the constraints, so having such an endpoint would then be a great motivation to migrate to that API. |
More research needed.
The text was updated successfully, but these errors were encountered: