You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2020/04/02 17:42:44 UTC
[GitHub] [couchdb] jaydoane commented on issue #2666: soft-deletion for
database
jaydoane commented on issue #2666: soft-deletion for database
URL: https://github.com/apache/couchdb/pull/2666#issuecomment-607996688
> I've also heard some concerns that having the `undelete` vs `delete` semantics of our `POST /_deleted_dbs` setup makes auditing traffic hard/impossible without introspecting the request body which seems like a legitimate critique. How about if we tweaked things to be like such:
>
> * `GET /_deleted_dbs` - List deleted dbs infos as currently.
>
> * `POST /_deleted_dbs` - Only accepts the `undelete` JSON body
>
> * `DELETE /_deleted_dbs/DbName?timestamp=2020-01-01T00:00:00` - Remove deleted db
I very much like this particular API, since it's trivial to derive three separate action names from method and path, unlike earlier versions. The corresponding names (eliding the ubiquitous `cloudantnosqldb.` prefix), I'm considering:
- `account-deleted-dbs.read`
- `account-deleted-dbs.undelete`
- `account-deleted-dbs.delete`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services