馃殌 Feature Description and Motivation
#1639 (comment)
The current user management API (/CreateUser, /ReadUser, etc., all using POST) is a direct migration from the previous Go service. While functional, it doesn't follow standard RESTful API design principles, which can make it less intuitive and harder for new developers to use.
Since this is a new Python service, it's a great opportunity to adopt a more standard RESTful approach. I suggest refactoring these endpoints to use standard HTTP methods and resource-based paths. For example:
- Create User: POST /v1/users
- Read User: GET /v1/users/{user_name}
- Update User: PUT /v1/users/{user_name}
- Delete User: DELETE /v1/users/{user_name}
This change would improve the API's clarity, predictability, and align it with modern web service best practices.
Use Case
user management for rate limits etc
Proposed Solution
No response
馃殌 Feature Description and Motivation
#1639 (comment)
The current user management API (/CreateUser, /ReadUser, etc., all using POST) is a direct migration from the previous Go service. While functional, it doesn't follow standard RESTful API design principles, which can make it less intuitive and harder for new developers to use.
Since this is a new Python service, it's a great opportunity to adopt a more standard RESTful approach. I suggest refactoring these endpoints to use standard HTTP methods and resource-based paths. For example:
This change would improve the API's clarity, predictability, and align it with modern web service best practices.
Use Case
user management for rate limits etc
Proposed Solution
No response