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

Drop getLink API call #148

Open
RKrahl opened this issue Dec 6, 2023 · 0 comments · May be fixed by #149
Open

Drop getLink API call #148

RKrahl opened this issue Dec 6, 2023 · 0 comments · May be fixed by #149
Labels
remove feature Proposal to remove some feature
Milestone

Comments

@RKrahl
Copy link
Member

RKrahl commented Dec 6, 2023

As already discussed during the collaboration meetings and announced via the mailing list: it seems that nobody is actually using the getLink API call. In that case, it is better to remove it.

In principle, it was not a bad idea to use hard links from the main storage to some user accessible directory to provide users a direct access to the file. But the current implementation in ids.server is somewhat to clumsy to be useful. It can be implemented as a separate script that could then be much easier adapted to the facility's needs. There is no need to have that integrated in ids.server.

According to current plans, we will deprecate that call in ids.server 2.0.0 and remove it in 3.0.0.

@RKrahl RKrahl added this to the 3.0.0 milestone Dec 6, 2023
@RKrahl RKrahl added the remove feature Proposal to remove some feature label Dec 6, 2023
@LewerenzM LewerenzM linked a pull request Dec 15, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
remove feature Proposal to remove some feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant