Create a design doc for the "MVP" scope of Object Lock implementation

[amwolff]

Goal

What this issue represents is the effort to create a blueprint to communicate with other teams wrt Object Lock.

What needs to be done? • Acceptance Criteria (+ Depends on…)

The design doc should talk about important decisions and ways to implement them for the "MVP" scope of Object Lock implementation. It should explain about why focus on the "MVP" scope of OL first, but it also needs to briefly talk about how we would implement the entire feature.

Make sure you follow the process.

Important topics to go through

1. The decision resulting from Decide where and make it possible to store per-object metadata for Object Lock #400
2. If there's any scope increase related to testing Create a gateway-only partial implementation of Object Lock #397
   1. https://github.com/storj/infra/issues/5594
3. satellite/libuplink (private?) API design?
   1. Object Versioning is a good example of how to approach this problem
4. Anything else that comes to your mind

Note

Try to keep the blueprint short and concise. Remember that the scope of the "MVP" implementation is extremely limited.

Links

• an easy-to-read and insightful introduction to Object Lock: Using S3 Object Lock

[amwolff]

Here's an internal link to the design draft.