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

Add HEAD endpoints for assets #409

Open
andrejridzik opened this issue Dec 5, 2024 · 0 comments
Open

Add HEAD endpoints for assets #409

andrejridzik opened this issue Dec 5, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@andrejridzik
Copy link
Collaborator

Describe the Feature
Adding HEAD endpoints for assets will be beneficial when only checking the existence of a specific asset without the need of retrieval of the entire asset JSON data.

An Example
The usage would be the same a the current GET asset endpoints, e.g. GET /datasets/v1/{identifier}

HEAD /datasets/v1/1234
HEAD /ml_models/v1/1234
...

Considered Alternatives
Alternative solution relies on using the GET endpoints and handling the 404 Not Found error.

Additional context
This operation is needed since the assets can be deleted in time and users/services need to be able to verify if a specific asset is still existent.

@andrejridzik andrejridzik added the enhancement New feature or request label Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant