From 7b268511c90ade4a2c00d1d751baf98a8cac0731 Mon Sep 17 00:00:00 2001 From: Stark & Wayne CI Bot Date: Thu, 17 Feb 2022 18:54:23 +0000 Subject: [PATCH] release v2.1.2 --- ci/release_notes.md | 34 ---------------------------------- ci/version | 2 +- 2 files changed, 1 insertion(+), 35 deletions(-) diff --git a/ci/release_notes.md b/ci/release_notes.md index b6fb5632..139597f9 100644 --- a/ci/release_notes.md +++ b/ci/release_notes.md @@ -1,36 +1,2 @@ -- Adds v1 vm support fix back in - - Better support for vm_types, especially in context of upgrading from v1 environments. - New feature `v1-vm-types` sets up the manifest to use the same VM types as was used in the v1.x versions of the kit, or as close to possible. This allows you to use your existing cloud config and tuning. Where the instance group name changes, it will use the vm type that the instance group was migrated from. - - The exceptions are `tcp-router`, which will use the `router` vm type, and `cc-worker` and `credhub`, which continue to use `minimum` as there was no prevous instance group for these functions. - - Fixes spelling of scheduler in MANUAL.MD - -- Removes references to adapter/syslogger instances/vms. - -This has been merged with syslog jobs as of cf-deployment v15.7.0, and implemented in v2.1.0 of this kit - -Bug Fixes: - -* Environments migrated from v1.x were suppose to retain the blobstore name - for the app packages blobstore (was -packages- in v1.x, - moved to -app-packages- to better match canonical in - v2.0.x for new environment). This has been restored. If you upgraded to - v2.0.x, you can keep the new blobstore name by adding the following to your - environment: - - ``` - meta: - blobstore_bucket_path: - app-packages: (( concat meta.blobstore_bucket_prefix "-app-packages-" meta.blobstore_bucket_suffix )) - ``` - -* Environments migrated from v1.x now correctly retain the original NATS user - credentials. Upstream used a different username, and as such, when - upgrading to v2.0.x, there was a loss of connectivity to NATS. Migrated - environments now retain the original v1.x username. - - If you have already upgraded your environment from v1.x to 2.0.x, you can - specify feature `v2-nats-credentials` to prevent NATS username from - switching back and causing further availability outage during deployment. diff --git a/ci/version b/ci/version index b48735db..f49cb4bf 100644 --- a/ci/version +++ b/ci/version @@ -1 +1 @@ -## Version: 2.1.1 +## Version: 2.1.2