56.6.0

Changes

In nats-release v46, we migrated the underlying binary from gnatsd (NATS v1), to nats-server (NATS v2). In this release, we are adding a post-start check that will fail the deployment if, for some reasons, NATS instances are running v1. This is a precursor to eventually removing the v1 binary and migration wrapper. The property defaults to false, but will default to true in cf-deployment.

If your instances are already running NATS v2, or if they successfully migrate to v2 in this release, you will not experience any change in behavior. If you want to confirm your NATS instances are on v2, follow the steps in this KB article.

Bosh Job Spec changes:

diff --git a/jobs/nats-tls/spec b/jobs/nats-tls/spec
index 0d25ad2..4f9b3b7 100644
--- a/jobs/nats-tls/spec
+++ b/jobs/nats-tls/spec
@@ -123,3 +123,6 @@ properties:
   nats.migrate_server.port:
     description: "Port for endpoint to migrate nats job to nats-server v2. To be removed in a future release."
     default: 4243
+  nats.fail_deployment_if_v1:
+    description: "Fail the deployment in post-start if nats instances are on v1."
+    default: false
diff --git a/jobs/nats/spec b/jobs/nats/spec
index e7d7a82..ddc54a3 100644
--- a/jobs/nats/spec
+++ b/jobs/nats/spec
@@ -116,3 +116,7 @@ properties:
     description: "The PEM-encoded certificate to use for verifying the TLS connection to the migrate server (used for local healthchecks)."
   nats.migrate_client.tls.private_key:
     description: "The PEM-encoded private key to use for verifying the TLS connection to the migrate server (used for local healthchecks)."
+  
+  nats.fail_deployment_if_v1:
+    description: "Fail the deployment in post-start if nats instances are on v1."
+    default: false

✨ Built with go 1.20.6

Full Changelog: v56.5.0...v56.6.0

Resources

• Download release v56.6.0 from bosh.io.