You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
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
The text was updated successfully, but these errors were encountered: