With #317 merged, we've finally merged a new endpoint into the backend API. And with that, it does seems that there's a few other endpoints we could implement.
Implementing additional endpoints will reduce the need for miscellaneous microservices to host full database credentials as well as improve the democratization of those endpoints, by allowing anyone with a proposed, singular admin key to making changes.
Those additional endpoints would look like:
- DELETE /api/users/states : Currently handled by
package-frontend/microservices/auth-state-cleanup to delete temporary authentication keys
- POST /api/packages/:packageName/badge : Endpoint to add a singular badge to a package. Currently handled by
package-backend-tools
- DELETE /api/packages/:packageName : Endpoint to delete a package entirely. While this one already exists, we likely should allow administrators access to this endpoint as well.
Again, these are all brand new proposed endpoints, taken from actions we already regularly take on the backend, that are currently done by misc. applications with full database access.
With #317 merged, we've finally merged a new endpoint into the backend API. And with that, it does seems that there's a few other endpoints we could implement.
Implementing additional endpoints will reduce the need for miscellaneous microservices to host full database credentials as well as improve the democratization of those endpoints, by allowing anyone with a proposed, singular
adminkey to making changes.Those additional endpoints would look like:
package-frontend/microservices/auth-state-cleanupto delete temporary authentication keyspackage-backend-toolsAgain, these are all brand new proposed endpoints, taken from actions we already regularly take on the backend, that are currently done by misc. applications with full database access.