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

feat: stream subsystem support tars service discovery #8826

Merged

Conversation

ronething
Copy link
Contributor

@ronething ronething commented Feb 10, 2023

Signed-off-by: ashing axingfly@gmail.com

Description

Fixes #7779

add tars service discovery, and it is the last PR for service discovery in the stream subsystem

for test case, i add stream_extra_init_by_lua_start to file APISIX.pm.

some code inspired by PR: #8640

Checklist

  • I have explained the need for this PR and the problem it solves
  • I have explained the changes or the new features added to this PR
  • I have added tests corresponding to this change
  • I have updated the documentation to reflect this change
  • I have verified that this change is backward compatible (If not, please discuss on the APISIX mailing list first)

Signed-off-by: ashing <axingfly@gmail.com>
@ronething ronething marked this pull request as ready for review February 10, 2023 08:16
schema.properties.full_fetch_interval.default = 3
_EOC_

$block->set_value("extra_init_by_lua_start", $extra_init_by_lua_start);
Copy link
Member

Choose a reason for hiding this comment

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

Why do we need to set the HTTP version in the stream test?

Copy link
Contributor Author

@ronething ronething Feb 14, 2023

Choose a reason for hiding this comment

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

The discovery configuration will affect both the HTTP and steam subsystem simultaneously. If we do not set extra_init_by_lua_start in HTTP, it will cause error like below.

nginx: [error] init_by_lua error: .../apisix/apisix/core/config_local.lua:71: invalid discovery tars configuration: property "full_fetch_interval" validation failed: expected 3 to be at least 90

@ronething
Copy link
Contributor Author

@soulbird Could you please take a look, thanks.

@spacewander spacewander merged commit 641481d into apache:master Feb 17, 2023
@ronething ronething deleted the feat/stream_route_discovery_tars branch February 17, 2023 02:15
hongbinhsu added a commit to fitphp/apix that referenced this pull request Feb 23, 2023
* upstream/master:
  fix: limit count plugin conf parameter undefined error (apache#8902)
  chore: remove duplicate kubernetes test case (apache#8882)
  feat: add 'range_id' algorithm for 'request-id' plugin (apache#8790)
  chore(error-log-logger): add kafka meta_refresh_interval (apache#8821)
  chore(deps): bump golang.org/x/net from 0.2.0 to 0.7.0 in /t/grpc_server_example (apache#8881)
  docs: Update getting-started.md (apache#8763)
  fix(admin): fix wrong http code for patch method (apache#8855)
  feat: stream subsystem support tars service discovery (apache#8826)
  feat(ci): implement image caching to reduce ci build time. (apache#8735)
  feat(admin): add head method support to /apisix/admin (apache#8752)
  feat: opentelemetry plugin config collector.address support specify https scheme (apache#8823)
  fix: add admin schema to control_plane config (apache#8809)
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.

feat: As a user, I want to support service discovery in the stream subsystem
3 participants