fix(worker): use deterministic volume naming for workflow execution #270
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.
Summary
tenantIdandrunIdderiveVolumeName()method toIsolatedContainerVolumeso downstream components (scanners) can reference volumes created by upstream components (clone-repo) in the same workflow execution without passing volume names through the graphrunIdis unique per workflow execution, timestamps are no longer needed to prevent collisionsTest plan
IsolatedContainerVolume.deriveVolumeName(tenantId, runId)returns consistent names