move render events to after template command #1370
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When using CT as a library, the "standard" way to monitor and know when to exit is to watch for messages on the TemplateRenderedCh(). The problem is that the message is sent down that channel before the commands are run, so the program could exit before the command has run. The problem is more obvious when CT is run in a transient container, where even if the commands are run the container might exit before they finish and they get killed. Moving the render events to after the command avoids these issues (the container exit issue also requires a command_timeout > 0s).
findkim
approved these changes
Apr 21, 2020
|
I'm going to update the PR to tweak to documentation to mention the 0s/fire-n-forget case. |
|
@findkim I updated the PR with the documentation change. |
jasonodonnell
approved these changes
Apr 21, 2020
This was referenced May 20, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using CT as a library, the "standard" way to monitor and know when
to exit is to watch for messages on the TemplateRenderedCh(). The
problem is that the message is sent down that channel before the
commands are run, so the program could exit before the command has run.
The problem is more obvious when CT is run in a transient container,
where even if the commands are run the container might exit before they
finish and they get killed.
Moving the render events to after the command avoids these issues (the
container exit issue also requires a command_timeout > 0s).
Fixes #1369