(I'm honestly not too familiar with the deis tls command so not sure if this is a flaky test or actual functionality bug. We can reassign if necessary.)
Deis Workflow.deis tls with an existing user who owns an existing app that has already been deployed can enable/disable tls has failed for the last 9 out of 14 e2e runs (as of writing)
let's skip the test for now and make sure we manually QA deis tls:disable to make sure it's actually working for the release, then come back to this for 2.6. Sounds fair?
(I'm honestly not too familiar with the
deis tls
command so not sure if this is a flaky test or actual functionality bug. We can reassign if necessary.)Deis Workflow.deis tls with an existing user who owns an existing app that has already been deployed can enable/disable tls
has failed for the last 9 out of 14 e2e runs (as of writing)Sample job: https://ci.deis.io/job/workflow-test-pr/6464/ Logs: https://ci.deis.io/job/workflow-test-pr/6464/artifact/6464/logs/
Output: