-
Notifications
You must be signed in to change notification settings - Fork 84
core: integration with Envoy's API listener #616
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
Changes from all commits
4e4ace3
20d3e1e
8418ee9
56914a0
62ebd14
fcb0870
76aee26
f069c82
f38e77c
cec541f
9b8b5e2
1ab5cd6
cf69083
85d1acf
3cd3a1a
c9721d9
e131965
f97b8b1
a98cfbf
5e740ae
e6d0d91
0f2ba0f
0ef3ef3
65b7ba9
58b60d1
96ca3ca
4ef47cb
ef68ba6
e0ac9cb
644d338
024f15b
ddf302b
413d813
c718e49
3ee492b
a3c2d8a
9fcbf08
191105a
f3d8ff2
ed88f67
8af70cf
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -64,7 +64,9 @@ envoy_status_t Engine::run(std::string config, std::string log_level) { | |
| postinit_callback_handler_ = main_common_->server()->lifecycleNotifier().registerCallback( | ||
| Envoy::Server::ServerLifecycleNotifier::Stage::PostInit, [this]() -> void { | ||
| Server::Instance* server = TS_UNCHECKED_READ(main_common_)->server(); | ||
| http_dispatcher_->ready(server->dispatcher(), server->clusterManager()); | ||
| auto api_listener = server->listenerManager().apiListener()->get().http(); | ||
| ASSERT(api_listener.has_value()); | ||
| http_dispatcher_->ready(server->dispatcher(), api_listener.value()); | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this additional delay (beyond construction) still necessary? We're no longer waiting on an initial round of DNS resolution and the filter dynamic forwarding filter contains built in buffering logic while we do wait. If we're unsure, maybe insert a TODO to follow up.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Still suggest adding a TODO and/or issue for this so we still have visibility to follow up. |
||
| }); | ||
| } // mutex_ | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.