fix bazel calls when using local envoy and --override_repository #2578
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.
What this PR does / why we need it:
For performing build/test operations with a local envoy source; one configured via the
--override_repository
flag.Otherwise, bazel will emit errors like:
ERROR: An error occurred during the fetch of repository 'envoy'
and
ERROR: no such package @envoy//...
on
bazel info
calls (since the override flag is unknown to the command) which is problematic for some/mostmake
targets that need to be aware of the envoy binary or bazel output locations.cc @howardjohn @yxue