Add TASK_ID environment variable with the singularity task_id#1170
Merged
Conversation
…ry docker container spawned for a request
Author
|
Our containers rely exclusively on the TASK_ID variable to do some cleanup when webhooks are triggered. I think it is a good addition, because I did not find a very straight forward way to get the exact TASK_ID for a request (there might be multiple tasks in a request) |
Author
|
Can we please get this small patch into 0.10? Having the actual TASK_ID accessible on every container is certainly helpful for referencing purposes. Thanks |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This could be helpful to get the actual TASK_ID of a Singularity task, rather than just the TASK_REQUEST_ID