forked from envoyproxy/envoy
-
Notifications
You must be signed in to change notification settings - Fork 62
Revert STS from 1.4 with cherry picks of integration and stress test fixes. #180
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
istio-testing
merged 11 commits into
istio:release-1.4
from
duderino:jblatt_revert_sts_and_fix_tests
Mar 4, 2020
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
8d3fb7c
Revert "fix opencensus tracer (#155)"
duderino 7cf7f62
Revert "Add x-goog-user-proj header for sts credential (#152)"
duderino c665445
Revert "Update GrpcService to add StsService. (#411)"
duderino 7a48ec8
Revert "fix tracer ssl credential (#151)"
duderino f0c8b8c
Revert "remove url validation as it is not implemented"
duderino 4e1e29f
Revert "Use gRPC Security Token Service (STS) to get call credentials…
duderino 6bdbf7a
Revert "[release-1.4] Use sts for call credential when STS_PORT is pr…
duderino bd68bad
Revert "Upgrade gRPC to 1.25 which has gRPC STS feature (#145)"
duderino 037cab7
ci: mark //test/integration:protocol_integration_test as flaky. (#162)
PiotrSikora 6a4f4fe
Remove wasm filter stress test
gargnupur 63302fd
Remove wasm stress test framework
gargnupur 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
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.
You shouldn't be reverting those changes, see: #175 (comment)
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.
But we didn't ship that in 1.4.6. I think instead we should get release-1.4 into a state that looks like the 1.4.6 release we just shipped, tag it, then reapply any fixes which can go out in 1.4.7
@howardjohn CC
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.
That's a valid point. OK, fair enough, no one should be using Wasm in 1.4 anyway...
cc @mandarjog @kyessenov @bianpengyuan for visibility.
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 disagree that we need to get release-1.4 branch into a state that looks like 1.4.6. We did not ship from 1.4 branch, as in reality we created a private 1.4.6 branch that was developed independently from 1.4 branch. Now that 1.4.6 branch is done, we should simply merge 1.4.6 branch into 1.4 branch (and that was exceptional due to secrecy around the patches).