When the ECS_IMAGE_PULL_BEHAVIOR is default and the image is large, starting a console can take more time than 30 seconds. This will lead to failure to start the container. This just loosens that startup timeout.
How to check that this is working?
Only the logic has changed. The manual test riggings no longer work so need to be updated. But the test mocks the process lister and checks that the process does what it does so go test needs to be good enough for now. I added more modern go-modules so you can use it if you have go installed locally. Otherwise brew install go.
When the ECS_IMAGE_PULL_BEHAVIOR is default and the image is large, starting a console can take more time than 30 seconds. This will lead to failure to start the container. This just loosens that startup timeout.
How to check that this is working?
Only the logic has changed. The manual test riggings no longer work so need to be updated. But the test mocks the process lister and checks that the process does what it does so
go test
needs to be good enough for now. I added more modern go-modules so you can use it if you have go installed locally. Otherwise brew install go.go build
go test