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

REST: allow production placeholder instead of version in addons custom endpoints #494

Open
alainxi opened this issue Jan 22, 2025 · 0 comments
Assignees

Comments

@alainxi
Copy link

alainxi commented Jan 22, 2025

Current situation :

Currently, paths to addon endpoints always contain the addon version, since all endpoints from all versions are always exposed.
Example : http:// myserverayon:5000/api/addons/my_addon/0.1.2/get-test-data/myProjectName

Problem :

If we code a custom endpoint, to be used by other departments, we can’t tell them it’s a moving target, they need a fixed url, as in usual REST APIs.
Because other departments can’t use self.version or similar, as the calls are done from other softwares.

Proposal

Please provide a “production" placeholder, that would replace the version.
Example : /api/addons/my_addon/production/my_endpoint

Context :

It was discussed here :

https://community.ynput.io/t/custom-endpoint/2149

@martastain martastain self-assigned this Jan 22, 2025
@martastain martastain changed the title custom endpoint url : allow production placeholder instead of version REST: allow production placeholder instead of version in addons custom endpoints Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants