Skip to content

Commit

Permalink
release v2.1.2
Browse files Browse the repository at this point in the history
  • Loading branch information
Stark & Wayne CI Bot committed Feb 17, 2022
1 parent df943d5 commit 7b26851
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 35 deletions.
34 changes: 0 additions & 34 deletions ci/release_notes.md
Original file line number Diff line number Diff line change
@@ -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 <prefix>-packages-<unique-id> in v1.x,
moved to <prefix>-app-packages-<unique-id> 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.
2 changes: 1 addition & 1 deletion ci/version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
## Version: 2.1.1
## Version: 2.1.2

0 comments on commit 7b26851

Please sign in to comment.