Add initial user-lists API endpoint#1734
Conversation
|
Drafting until DB changes are in. Did one endpoint to start so i can check performance of the endpoints as I go. |
MikeNeilson
left a comment
There was a problem hiding this comment.
Seems like a reasonable start.
| crud("/users/{user-name}", new UsersController(metrics), adminRoles); | ||
| get("/roles", new GetRolesController(metrics), adminRoles); | ||
| get("/user/profile", new UserProfileController(metrics), userRoles); | ||
| get("/user/list/{user-list-id}/members", new UserListMembersController(metrics), adminRoles); |
There was a problem hiding this comment.
long term, I'd probably group these by "/user/list" rather that method -> "/user/..."
But that's just me.
|
Added the next user-list GET endpoint under /user/list: GET /user/list/{user-list-id}?office={office} Returns metadata for a single office-scoped user list Separate from the existing members endpoint. EDIT: Going to resolve conflicts at the end when it's ready for merge (not draft) |
|
Spoke with Mike N on 07/24/2026 Needs to be behind a feature flag (togglez) to make sure the DB has it. This will make it not show it in swagger. and a proper unsupported response. Minimum schema version enum. Also to go ahead and PR this to have all the GET/POST/DELETE/etc for one larger review. All the user stuff should have add user handlers/function for grouping so things are more clear. |
Refs #1733.
Summary
This draft PR adds the first
user-listsAPI endpoint:GET /user/list/{user-list-id}/members?office={office-id}What Changed
UserListMembersControllerUserListDaoUserListMemberandUserListMembersDTOsApiServletuser-list-idcontroller constantNotes
user-listsfeature workHydrologicEngineeringCenter/cwms-database#159user-id,full-name, andemailValidation
./gradlew :cwms-data-api:compileJavauser-listsdatabase schemadata-apicontainer and confirmed the route appears in Swagger/OpenAPIFollow-up
Additional endpoints will be added in separate commits, one method/endpoint at a time.