Compose parameter pause-after-phase

[davidkopp]

There is a compose parameter pause-after-phase, but it is not documented and there is no example available.
For which scenarios was this implemented? Is this a parameter that should be used by users of GMT?

It was introduced with the following commit by @ribalba :
green-coding-solutions/green-metrics-tool@4c89f26

[ArneTR]

The parameter in the usage_scenario is currently undocumented as we needed it for an internal feature and it is not well tested.

The case was that we had a container that was doing some preparation work and cache warming in the installation and boot phase. After that it should not be be lingering around anymore.

Since the GMT expects all containers to be present from start to end and fails if the suddenly disappear this parameter allows for a container to bail out after a defined phase.

This needs a documentation and a test case. If you want to use the parameter in your current tests you can use it. It should work as intended, but we cannot provide a test guarantee for it atm.

Thanks for bringing this up. Leaving the Issue open as help wanted. If more people comment we will prioritize this issue.