-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on performing "deepify publish" action #365
Comments
@eistrati the answer is yes, but unfortunately it did not help on resolving this issue |
According to the answer on the case https://console.aws.amazon.com/support/home?region=us-east-1#/case/?displayId=2171732401&language=en we can't use both custom api domains and blue-green deployment simultaneously |
@AlexanderC Let's rethink blue-green deployment by avoiding wild carded SSL in CF distribution |
According to AWS Partners webinar meeting notes they are going to separate Api Gateway & CloudFront. Than should solve the issue with wildcard certificate ( FYI The bug was not related to the certificate itself but to the way Api Gateway is creating custom domains (a top level in spite the 3'rd level specified). @eistrati Could you please review the task and let me know if it is still relevant? |
Let's put this on hold and wait until AWS releases this feature, so we can go back and refactor |
Pre-requisites:
Steps to reproduce:
deepify publish --blue e6c23ab8 --green 67d9c6d3 --data-replicate true --ratio 4:1
Note:
Please refer to attachment for more details:
The text was updated successfully, but these errors were encountered: