Skip to content
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

bazel\repositories: Update to envoy-fork to pick up callback commit for caching #158

Closed
wants to merge 1 commit into from

Conversation

nfuden
Copy link
Collaborator

@nfuden nfuden commented Apr 4, 2022

Should have done this instead of the normal upgrade to 1.21
That being said this singular commit didnt make it into upstreams 1.21 release by a couple days so needs to exist here for caching in envoy-gloo-ee

Comment on lines +4 to +5
commit = "584a730c320c80e44514450f71344549c01722a6",
remote = "https://github.com/solo-io/envoy-fork",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we moving to the fork? This got merged upstream

@nfuden
Copy link
Collaborator Author

nfuden commented Apr 5, 2022

I was bad. I looked at times of 1.21.1 and also checked in for the existence of one of the two upstream PRs that you made.

Unfortunately when rebuilding Enterprise envoy-gloo with caching I kept hitting an issue that I was sure wasnt the case until I actually looked correctly.
Namely envoyproxy/envoy@38d5b52 was merged days after 1.21 cut https://github.com/envoyproxy/envoy/releases/tag/v1.21.0
So this is just the streamfilter callbacks being added.

@EItanya
Copy link
Member

EItanya commented Apr 5, 2022

Master in envoy is considered safe to use iirc, especially in betas, so we can probably use that

@nfuden nfuden closed this Jun 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants