StreamConfig adds `discard_new_per_subject: boolean` on servers 2.9.2 and better

[aricart]

Overview

Stream configuration now adds the boolean property discard_new_per_subject. This new option works in conjunction of the discard and it is not valid (rejected by the server) if the discard policy is not new.

The new option will prevent a message from being added to a stream if the max_msgs_per_subject limit for the subject has been reached, returning a {"error":{"code":503,"err_code":10077,"description":"maximum messages per subject exceeded"}, "stream":"KV_A","seq":0}

Clients and Tools

• [x] Schemas @ripienaar
• [x] CLI @ripienaar
• [x] Terraform @ripienaar https://github.com/nats-io/terraform-provider-jetstream/pull/68
• [x] Github Actions @ripienaar
• [x] Go @piotrpio https://github.com/nats-io/nats.go/pull/1102
• [x] Java @scottf https://github.com/nats-io/nats.java/pull/755
• [x] JavaScript @aricart https://github.com/nats-io/nats.deno/pull/373
• [x] .Net @scottf https://github.com/nats-io/nats.net/pull/691
• [x] C done by kozlovic https://github.com/nats-io/nats.c/pull/593
• [ ] Python @wallyqs
• [ ] Ruby @wallyqs
• [x] Rust @Jarema @caspervonb

Other Tasks

• [ ] docs.nats.io updated @jnmoyne
• [ ] 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.