Skip to content
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

Open
avozicov opened this issue Apr 26, 2017 · 6 comments
Open

Error on performing "deepify publish" action #365

avozicov opened this issue Apr 26, 2017 · 6 comments

Comments

@avozicov
Copy link
Contributor

Pre-requisites:

  • Two instance of application is required to be deployed (blue / green)

Steps to reproduce:

  • From the application directory execute the following command :
    deepify publish --blue e6c23ab8 --green 67d9c6d3 --data-replicate true --ratio 4:1

Note:

  • you can use the provided hash because it is deployed app hash which is used for testing purposes

Please refer to attachment for more details:
screen shot 2017-04-26 at 14 55 10
screen shot 2017-04-26 at 14 54 50

@eistrati
Copy link
Contributor

@CCristi @avozicov Did you guys try to remove "adtechmedia.io" CNAME and try again?

@avozicov
Copy link
Contributor Author

@eistrati the answer is yes, but unfortunately it did not help on resolving this issue

@AlexanderC
Copy link
Contributor

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

@eistrati
Copy link
Contributor

eistrati commented May 1, 2017

@AlexanderC Let's rethink blue-green deployment by avoiding wild carded SSL in CF distribution

@AlexanderC
Copy link
Contributor

According to AWS Partners webinar meeting notes they are going to separate Api Gateway & CloudFront. Than should solve the issue with wildcard certificate (*.adtechmedia.io).

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?

@AlexanderC AlexanderC assigned eistrati and unassigned AlexanderC May 30, 2017
@eistrati
Copy link
Contributor

Let's put this on hold and wait until AWS releases this feature, so we can go back and refactor

@ivignan ivignan added the on hold label Jun 4, 2017
@ivignan ivignan removed this from the Milestone #3 - May milestone Jun 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants