feat: add force_local_execution attribute to copy rules & macros for opt-out of local execution requirements #605
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.
There are use cases where copy rules should run sandboxed or on remote executors. In these cases users should set
force_local_execution
to False so the rules are not opinionated. Users can set custom execution requirements in their bazelrc via mnemonics if desired. Forcing local execution still seems like the best default for best performance by default when #466 is not an issue.Related issues & threads,
#466
https://bazelbuild.slack.com/archives/CEZUUKQ6P/p1694892563112649
Type of change
Test plan