Jose Diaz-Gonzalez 82dfcc01e2 fix: handle udp ports when fetching network config ...

When an app only has UDP ports exposed, deploys will fail as we expect there to be a single TCP port.

While we _should_ support both, the easier fix is to ignore things and move on. Users can manually expose UDP ports as necessary via the -p flag (or by not specifying the port as a UDP port).

One quirk discovered during tests is that disabling zero-downtime deploys results in odd output, but also a deploy can succeed even if one of the processes that skipped zero-downtime fails. We should fix this in another PR, but this is documented in tests for now.

Closes #4804

2021-09-29 00:37:38 -04:00

6.4 KiB

Raw Blame History

View Raw