[Blue-Green] Start 3rd CF distribution in parallel with CNAME change

[eistrati]

Let's improve blue-green deployment process by starting in parallel 3rd CF distribution and change CNAGE on blue CF distribution. Don't specify any CNAME for 3rd distribution, but rather make a change later when updating DNS records in Route53.

Here below is current situation that needs to be improved:

MitocGroup:~ eugene$ deepify publish -b 4f52a980 -g d1363c23 -r 1:1
08:26:36 GMT-0400 (EDT) Changing blue distribution CNAMEs to wildcarded
Following Route53 actions are going to be executed:
CREATE blue1.deep.mg of type A alias for d2k6750hkce0i8.cloudfront.net.
Please confirm those changes (Y/N): y
08:26:46 GMT-0400 (EDT) Waiting for CloudFront distribution EE0C1PRR1YUFY to be deployed (currently InProgress, ETC 20 min)
[...]
08:45:23 GMT-0400 (EDT) Waiting for CloudFront distribution EE0C1PRR1YUFY to be deployed (currently InProgress, ETC 1.5 min)
08:45:53 GMT-0400 (EDT) Creating 3rd cloudfront distribution for blue green traffic management
08:45:57 GMT-0400 (EDT) Attaching "DeepDevCloudfrontTrafficManager01454f52a980" to E1GPJZQJRYEN31 viewer-request event.
08:46:00 GMT-0400 (EDT) Function "DeepDevCloudfrontTrafficManager01454f52a980 has been attached to E1GPJZQJRYEN31 viewer-request event.
08:46:00 GMT-0400 (EDT) Waiting for CloudFront distribution E1GPJZQJRYEN31 to be deployed (currently InProgress, ETC 20 min)
[...]
09:24:43 GMT-0400 (EDT) Waiting for CloudFront distribution E1GPJZQJRYEN31 to be deployed (currently InProgress, ETC ...)
Following Route53 actions are going to be executed:
UPSERT blue.deep.mg. of type A alias change to d1ilt2c3mlv9pp.cloudfront.net
Please confirm those changes (Y/N): y
14:58:04 GMT-0400 (EDT) Blue green traffic management has been enabled. d2k6750hkce0i8.cloudfront.net (50%) AND d2l9qjqhlw5shj.cloudfront.net (50%)

[avozicov]

Test actions is blocked by the following issue:
https://github.com/MitocGroup/deepify/issues/365

[avozicov]

@eugene @igor
As I have mentioned in the previous comment - the reason why this issue was not tested is that is blocked by the the following issues:
#365

[ivignan]

Not relevant anymore.