The recycle bin is currently a dynamic route generated by a *Common object created inside of routeconfig. As such, there is no package or unique functions associated with it.
The original plan was to leverage the lbAPI Web UI, and limit operations to a simple DELETE record from recycle and CREATE record using previous data payload. This would then leverage the existing DELETE and CREATE handlers already associated with the virtualserver and recycle routes.
There is also a valid argument to include a recycle package that supports arguments passed to the recycle route that automatically performs the necessary calls and checks to restore the deleted record.
WANT
Pros/Cons on creating a dedicated package or leaving it as independent actions that can be instrumented via the web UI
The recycle bin is currently a dynamic route generated by a
*Common objectcreated inside ofrouteconfig. As such, there is no package or unique functions associated with it.The original plan was to leverage the lbAPI Web UI, and limit operations to a simple DELETE record from recycle and CREATE record using previous data payload. This would then leverage the existing DELETE and CREATE handlers already associated with the
virtualserverandrecycleroutes.There is also a valid argument to include a
recyclepackage that supports arguments passed to therecycleroute that automatically performs the necessary calls and checks to restore the deleted record.WANT