tree 32ef39d66d80995d59330697ab25fc9d9a2b3229
parent 25caaf99a6803ee664b71e1f06babb0a3adfc6a6
author Justin Berstler <bjustin@us.ibm.com> 1487710305 -0500
committer Perry <perry@us.ibm.com> 1487954707 -0500

Do not retry /run on action containers

It should be assumed that /run only happens after /init which should itself ensure that the container is running and ready. With that in mind, it does not make sense to attempt to retry posting to the /run endpoint on connection failures. Such a failure is an indication that something catastrophic has happened to the container, and no attempt at recovery should be made.

This is accomplished by adding a "retry" flag to the appropriate HTTP utilities to control whether or not a retry should be attempted.