Describe the feature
Right now, to get a boot script using the non-legacy API, the endpoint is /boot/v1/bootscript. The boot-service should have it's own endpoint paths that are not tied to the BSS legacy ones.
I would like to update the boot script API to something like /bootscript and only use /boot/v1/bootscript when the legacy API is enabled.
Why do you want this feature?
This would eliminate confusion on why /boot/v1/ endpoints would still be present even with the legacy API disabled. Plus, /boot/v1 is BSS-specific and the boot-service endpoints should follow its own conventions for endpoint paths.
Alternatives you've considered
We could leave it, but the general consensus seems to be moving away from legacy endpoints.
Additional context
No response
Code of Conduct
Describe the feature
Right now, to get a boot script using the non-legacy API, the endpoint is
/boot/v1/bootscript. The boot-service should have it's own endpoint paths that are not tied to the BSS legacy ones.I would like to update the boot script API to something like
/bootscriptand only use/boot/v1/bootscriptwhen the legacy API is enabled.Why do you want this feature?
This would eliminate confusion on why
/boot/v1/endpoints would still be present even with the legacy API disabled. Plus,/boot/v1is BSS-specific and the boot-service endpoints should follow its own conventions for endpoint paths.Alternatives you've considered
We could leave it, but the general consensus seems to be moving away from legacy endpoints.
Additional context
No response
Code of Conduct