-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Update data-plane-api #2430
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Update data-plane-api #2430
Changes from 20 commits
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
7541aad
working towards proto update
kyessenov e3c4001
progress
kyessenov d0f62f0
progress
kyessenov fbd77e9
progress
kyessenov 80fcb91
progress
kyessenov ce786ca
progress
kyessenov eabc99d
progress
kyessenov 24ffa46
fixes
kyessenov 15f44f0
fix with dummies
kyessenov c598074
merge conflict
kyessenov b169355
fix format
kyessenov 868efd2
fix test
kyessenov aab9bb7
merge fix
kyessenov b0b5850
fix build
kyessenov 4c15565
fix import
kyessenov afcb07c
merge fix
kyessenov 1a8e782
comment fix
kyessenov a134b4b
bad merge
kyessenov d4540cd
fix doc
kyessenov 51e0bcf
push dummies to the source out of tests
kyessenov 4dde384
merge fix
kyessenov 0ed8cf5
merge fix
kyessenov ffc0a6b
remove api binds
kyessenov 460f141
Merge remote-tracking branch 'upstream/master' into packages
kyessenov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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 was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd be happy to clean this up separately to avoid binding so many names...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, yes please
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer not using binds (I think they might be an antipattern as they make working with multiple workspaces difficult). We should use "actual" names, since the path is more or less stable.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, yeah, some history here. When we first started to Bazelify Envoy, it was unclear to me how best to handle external deps from a few perspectives:
Bind made sense at that time as an indirection mechanism to provide flexibility.
The prebuilt situation has stabilized and doesn't apply here (we don't prebuild
@envoy_api). The import for Google is also now moot. While it's a little neater to rebind, TBH we're sed-ing a ton during the import, so rewriting@envoy_apiis trivial.So, definitely for this dependency, which is now sprawling with binds, let's just switch to direct reference to @envoy_api everywhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 if we can just do this now since this is already a giant change and mostly find/replace. I wondered why we did this in the first place, thanks for the explanation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done, with a sed swoosh