Merge pull request #224 from carpawell/fix/clarify-container-removal

Fix/Clarify container removal

Author: roman-khimov

container/service.proto

@@ -30,6 +30,9 @@ service ContainerService {
   // response immediately. After a new block is issued in sidechain, request is
   // verified by Inner Ring nodes. After one more block in sidechain, the container
   // is added into smart contract storage.
+  // NOTE: a container deletion leads to the removal of every object in that
+  // container, regardless of any restrictions on the object removal (e.g. lock/locked
+  // object would be also removed).
   //
   // Statuses:
   // - **OK** (0, SECTION_SUCCESS): \

lock/types.proto

@@ -11,6 +11,8 @@ import "refs/types.proto";
 // lock object is limited similar to regular objects in
 // `__NEOFS__EXPIRATION_EPOCH` attribute. Lock object MUST have expiration epoch.
 // It is impossible to delete a lock object via ObjectService.Delete RPC call.
+// Deleting a container containing lock/locked objects results in their removal
+// too, regardless of their expiration epochs.
 message Lock {
   // List of objects to lock. Must not be empty or carry empty IDs.
   // All members must be of the `REGULAR` type.