Build configurtion issue

[bytebeast]

Hi,

I am currently working on a solution to the following issue related to build configuration. In my project, the top-level (parent) BUILD file defines a python_binary target and its corresponding dependencies, which reference targets located in subdirectories. However, these sub-directory BUILD files reside in shared directories that are not under my control, as they are used by multiple projects.

Recently, changes were made to the pip_library versions defined in those sub-directory BUILD files, which have introduced compatibility issues in my project. While I have identified a fix that involves modifying the package versions, applying this fix directly in the sub-directories could potentially break other dependent projects.

My objective is to override the pip_library versions at the parent level without modifying the shared subdirectory BUILD files. What is the recommended approach to override or pin specific pip_library versions in the parent BUILD file so that they take precedence during the build process?

Updating our code to work with changes made to package versions in sub-directories is currently not an option.

parentDir/
├── BUILD
├── subDir1
│   └── BUILD
└── subDir2
    └── BUILD

[SimonNungwa]

BAZEL has an override repository rule, you can override a repo definition globally