DEVPROD-26391 Expand BV module list names #9790
Merged
Conversation
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
# Conflicts: # config.go
Kimchelly
reviewed
Feb 10, 2026
Contributor
Kimchelly
left a comment
Kimchelly
left a comment
There was a problem hiding this comment.
If we expand the module list during task setup, is the logic to expand the module list during git.get_project now redundant?
# Conflicts: # config.go
Contributor
Author
Yes, good catch, I removed instances of duplicate expansion of module names |
Kimchelly
approved these changes
Feb 12, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
DEVPROD-26391
Description
When a downstream patch is scheduled, for example in Pine, the module list is an expansion set via the downstream parameters feature. But the module list is never expanded, so when the pine task runs the task logs show a warning because the module is not recognized as included in the BV module list:
Hence, projects like pine are not able to run off of the changeset from their parent. And changes that break pine are not discoverable until post-merge.
Solution
Expand the module list!
Testing
Verified in sandbox staging 1) repro of the bug and 2) that this change fixes it