fix(worker): use deterministic volume naming for workflow execution#270
Merged
fix(worker): use deterministic volume naming for workflow execution#270
Conversation
Replace timestamp-based volume naming with deterministic names derived from tenantId and runId. This allows downstream components (scanners) to reference volumes created by upstream components (clone-repo) in the same workflow execution without passing volume names through the graph. Add static deriveVolumeName() method so any component can compute the expected volume name from context. Signed-off-by: Aseem Shrey <LuD1161@users.noreply.github.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 66619c7bd1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
2 tasks
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
1 participant
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