[BSC#1107545] Migrate subnet pillar name v2.1 -> v3

SUSE / velum

Dashboard for CaaS Platform clusters (v1, v2 and v3)

https://www.suse.com/

Apache License 2.0

54 stars 30 forks source link

[BSC#1107545] Migrate subnet pillar name v2.1 -> v3 #650

Closed bear454 closed 5 years ago

bear454 commented 5 years ago

In v3, the subnet ID is stored in the same Pillar for all public clouds, then arranged into the appropriate pillar structure by InternalApi::V1::PillarsController#cloud_framework_contents

In v2.1, AWS had a different name for the subnet ID (for Azure & GCP, the name is consistent); therefore it is necessary to modify the pillar, if already assigned, in order to prevent losing the customer's entered data.

bear454 commented 5 years ago

Bug 1107545 - migration from v2.1 to v3 will lose AWS subnet id

jordimassaguerpla commented 5 years ago

Merging. This has been approved and the tests pass.