W-17856636-VPC-Upgrade-Changes #777
Conversation
|
|
||
| When upgrading your CloudHub VPC to a CloudHub 2.0 private space, the environments associated with your VPC stays in sync with the environments associated with the upgraded CloudHub 2.0 private space to avoid configuration drift. | ||
|
|
||
| Environment association works differently in xref:cloudhub-2::ps-config-env.adoc[CloudHub 2.0] and xref:vpc-tutorial.adoc#update-an-existing-anypoint-vpc[CloudHub 1.0]. In CloudHub 2.0, an environment can be associated with multiple: whereas iin CloudHub, an environment can be associated to only one VPC. |
There was a problem hiding this comment.
In CloudHub 2.0, one environment can be associated with multiple private spaces, whereas in Cloudhub 1.0, one environment can only be associated with one VPC in a given region.
|
|
||
| Environment association works differently in xref:cloudhub-2::ps-config-env.adoc[CloudHub 2.0] and xref:vpc-tutorial.adoc#update-an-existing-anypoint-vpc[CloudHub 1.0]. In CloudHub 2.0, an environment can be associated with multiple: whereas iin CloudHub, an environment can be associated to only one VPC. | ||
|
|
||
| === Upgrading the Default VPC |
There was a problem hiding this comment.
Remove this entire section, as we are not allowing upgrading default VPC. We can go with the Warning section below.
|
|
||
| == Understand Environment Association | ||
|
|
||
| When upgrading your CloudHub VPC to a CloudHub 2.0 private space, the environments associated with your VPC stays in sync with the environments associated with the upgraded CloudHub 2.0 private space to avoid configuration drift. |
There was a problem hiding this comment.
- to avoid confusion, can we explicitly say,
When Upgrading & while upgrade is in progress i.e. CloudHub VPC & CloudHub 2.0 Private Space coexist... - Can we also mention a point that if user associates bulk association on their CloudHub 2.0 Private Space, to avoid drift, tool will appropriately associate individual associations to the CloudHub VPC counterpart to avoid drift
There was a problem hiding this comment.
For 1, we could say something like During the upgrade process from CloudHub VPC to CloudHub 2.0 Private Space, the environments associated with your VPC stays in sync with the environments associated with the upgraded CloudHub 2.0 private space to avoid configuration drift.
For 2, we should add this line Additionally doing bulk environment associations for an upgraded Private Space can result in all environments in the same region to get associated with the underlying VPC. If those environments were previously associated with other CloudHub 1.0 VPCs, they will be disassociated.
There was a problem hiding this comment.
On 2 better would be:
Additionally doing bulk environment associations for an upgraded Private Space will result in environments getting associated with the underlying VPC. If those environments were previously associated with other CloudHub 1.0 VPCs in the same region, they will be disassociated.
Co-authored-by: Daniela Merlo <97902112+dmerlob@users.noreply.github.com>
luanamulesoft
dismissed stale reviews from dmerlob and aishwarya-murali
via
23fda15
Co-authored-by: Daniela Merlo <97902112+dmerlob@users.noreply.github.com>
4 participants
Writer's Quality Checklist
Before merging your PR, did you: