Open i030336 opened 6 years ago
Not sure if this is related, but as of last week, we've been unable to run blue-green deploys because the '-new' route is taken. We're getting the following error, "Could not push new version - Server error, status code: 400, error code: 210003, message: The host is taken: app-name-new"
dallashudgens did you find solution for this?
Someone can create (and reserve) the alternative route required for blue-green deployment: "-new", thus compromising blue-green deployment (since the routes are unique per landscape).
My proposal is to skip removing of the route after smoke test execution and only unbind it from the application. This way the alternative route will be reserved too for any future blue-green deployment, preventing any malicious software to reserve it and compromise blue-green deployment. Or at least there should be parameter to control this, similar to --keep-old-apps