gomod(deps): bump github.com/nats-io/nats-server/v2 from 2.8.4 to 2.9.0 in /components/event-publisher-proxy

[dependabot]

Bumps github.com/nats-io/nats-server/v2 from 2.8.4 to 2.9.0.

Release notes

Sourced from github.com/nats-io/nats-server/v2's releases.

Release v2.9.0

Changelog

IMPORTANT NOTE: Leafnode connections will now be closed if the cluster name is detected to be the same on the "hub" and "spoke", and reconnect attempts will be delayed by 30 seconds. If you are unaware of this misconfiguration you may experience a split network for longer than expected during the upgrade process. See the CHANGED section below and more details in pull request #3232.

Go Version

• 1.19.1: Both release executables and Docker images are built with this Go release.

Added

• JetStream:
  • A new stream configuration field AllowDirect allows capable client libraries to have a new API that retrieves a message from any member of the group (leader or replicas). Note that this can lead to non-coherent reads after write since a replica may respond to the request although that replica does not yet have the latest write. The configuration field MirrorDirect allow the mirror to be part of the origin's group (#3158, #3221, #3238, #3247, #3252, #3325, #3329, #3358, #3380, #3392, #3441)
  • Support for InactiveThreshold for durable consumers. If the inactivity threshold is specified, a durable that is offline for more than this duration will be removed (#3190)
  • Ability for an operator to move streams, and support for tags reload (#3217, #3236, #3234, #3270, #3354, #3376, #3419)
  • Support for filter subject in a mirror configuration (#3227)
  • Support for consumer replica change. Thanks to @​goku321 for the report (#3293)
  • Support for account purge operation by sending a request to $JS.API.ACCOUNT.PURGE.<account name>. Thanks to @​goku321 and @​sourabhaggrawal for the report (#3319, #3378)
  • Support for AES-GCM cipher encryption for FileStore (#3371)
  • Ability to override the default server limit for stream catchup. For instance jetstream: { max_outstanding_catchup: 32MB }. This limit is how many bytes in total may be inflight during streams catchup. This can help lower network bandwidth saturation (#3418)
  • Pagination for StreamInfo requests. Note that not all clients may have the ability to provide the offset at the time of the server release (#3454)
• LeafNodes:
  • Support for a SignatureHandler in remote configurations. This is applicable to applications embedding the NATS Server. Thanks to @​kung-foo for the suggestion (#3335)
• Monitoring:
  • Account specific in/out messages/bytes and slow consumers statistics in $SYS.ACCOUNT.%s.SERVER.CONNS message response (#3187)
  • New endpoint /accstatz to get specific account statistics (such as number of connections, messages/bytes in/out, etc...) (#3250, #3382)
  • The /healthz endpoint is now also available via the system account under the $SYS.REQ.SERVER.PING.HEALTHZ subject (#3250)
  • New options for the /healthz endpoint: /healthz?js-enabled=true to return an error if JetStream is disabled, and /healthz?js-server-only=true to skip the check of JetStream accounts, streams and consumers. Thanks to @​mfaizanse for the contribution (#3326)
  • The /connz?auth=1 endpoint now includes a tls_peer_certs array with subject, subject public key and raw certificate sha256. Thanks to @​RedShift1 for the suggestion (#3387)
  • The /jsz?accounts=true endpoint will now show non 0 values for reserved_memory and reserved_storage when applicable (#3435)
• MQTT:
  • A new configuration option consumer_inactive_threshold allow new QoS1 consumers to be removed if they are offline for more than the specified duration (based on #3190) (#3193)
• Use of a library that automatically sets GOMAXPROCS to match Linux container CPU quota. Thanks to @​1995parham for the contribution (#3218, #3224, #3237, #3406)
• A new server configuration option DontListen that triggers the server to accept only "in memory" client connections. This is for embedded use-cases only and is paired with changes made in the client library nats.go. Thanks to @​neilalexander for the contribution (#2360, #3225)
• Support for JWT account option DisallowBearer (#3127)
• Stubs for WebAssembly. This allows NATS Server to be built under the js/wasm target. Thanks to @​neilalexander for the contribution (#2363)
• Symlink for the deb/rpm packages. Since v2.7.4, the server is installed under /usr/bin instead of /usr/local/bin as it used to. We now have added symlink to /usr/local/sbin. Thanks to @​ismail0352 for the report (#3242)
• Templates to scoped signing key user permissions (#3367, #3373, #3390)
• New subject mapping functions: SplitFromLeft, SplitFromRight, SliceFromLeft, SliceFromRight and Split (#3305)
• Building of executable, deb and rpm packages for the s390x architecture (#3458)

Changed

• Gateway:
  • Phasing out of the "optimistic" mode whereby a server could send messages to the remote cluster without knowing if there was an interest or not. The remote cluster would reply with a "no interest" protocol. As of v2.9.0, servers that creates a gateway connection to a server of that version (and above) will no longer send messages in optimistic mode since it is assumed that all accounts will be switched to interest-only mode (where the subscription interest map is sent over) (#3383)
• JetStream:
  • Stream's RePublish configuration field is now a new RePublish object (and SubjectMapping has been removed) that allows for a new boolean field called HeadersOnly. This could be useful for large messages and having republish just be a signaling mechanism (#3157)
  • When a pull request exceeds the maximum bytes, the error returned will be a "409" now instead of a "408" (#3172)
  • Make pull consumers FIFO per message, not per request (#3241)
  • Accept Nats-Expected-Last-Sequence with a 0 value. The server used to ignore if the sequence was 0, but now it will treat it as a requirement that the stream be empty if the header is present with a value of 0. Thanks to @​bruth for the suggestion (#3038)
  • A consumer "Maximum Deliveries" count can now be updated. Thanks to @​abegaj for the contribution (#3265)

... (truncated)

Commits

• 517d9b3 Merge pull request #3460 from nats-io/release_2_9_0
• b979556 Release v2.9.0
• f7cb5b1 changed format of JSClusterNoPeers error (#3459)
• 50d62ce Merge pull request #3458 from nats-io/add_s390x_arch
• d4f2b17 [ADDED] Architecture s390x in goreleaser.yml file
• fdf5255 Bump to 2.9.0-RC.19
• d979937 Merge pull request #3456 from nats-io/max-bytes-pull
• dedf21d Fix for issue #3455
• b32814d Better accounting for max-bytes for pull consumers
• ae0d808 Merge pull request #3457 from nats-io/cleanup_tests
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[mfaizanse]

Blocked by: #15476

[kyma-bot]

@dependabot[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-telemetry-operator-unit-test	ebcaabb	link	true	/test pull-telemetry-operator-unit-test
pull-compass-runtime-agent-unit-test	ebcaabb	link	true	/test pull-compass-runtime-agent-unit-test
pull-event-publisher-proxy-unit-test	ebcaabb	link	true	/test pull-event-publisher-proxy-unit-test
pull-function-controller-unit-test	ebcaabb	link	true	/test pull-function-controller-unit-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[dependabot]

Superseded by #15627.