ObjectStore `put` doesn't have `previousRevision`

[aricart]

Overview

For object store, we are missing a previousRevision option for put. Without it, it is very possible to create object store entries that are unable to prune the previous entry, as the put operation determines if the object exists at the start of the operation. This means that if another operation is in flight, the data for the object be leaked on the stream as the client that writes the last entry will win effectively making the chunk data invisible.

The implementation for object store is exactly the same as the put option in KV.

Clients and Tools

• [ ] Schemas @ripienaar
• [ ] CLI @ripienaar
• [ ] Terraform @ripienaar
• [ ] Github Actions @ripienaar
• [ ] Go @piotrpio
• [ ] Java @scottf
• [X] JavaScript @aricart https://github.com/nats-io/nats.deno/pull/471
• [ ] .Net @scottf
• [ ] C @levb
• [ ] Python @wallyqs
• [ ] Ruby @wallyqs
• [ ] Rust @Jarema @caspervonb

Other Tasks

• [ ] docs.nats.io updated @bruth
• [ ] Update ADR to Implemented
• [ ] Update client features spreadsheet

Client authors please update with your progress. If you open issues in your own repositories as a result of this request, please link them to this one by pasting the issue URL in a comment or main issue description.

[scottf]

There is no put with revision in KV. There is create which requires no revisions exist for a key. There is update, which requires matching the previous revision.

So do you mean to make parallel for OS, or did you really specifically mean put with revision?