Skip to content

fix(apisix-standalone): conflict between upstream nodes and service discovery #344

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.

Sign up for GitHub

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 1 commit into from
Sep 25, 2025
Merged

fix(apisix-standalone): conflict between upstream nodes and service discovery #344

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions libs/backend-apisix-standalone/src/transformer.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,14 +28,18 @@ export const toADC = (input: typing.APISIXStandalone) => {
pass_host: upstream.pass_host,
upstream_host: upstream.upstream_host,

// Empty Lua tables will be encoded as "{}" rather than "[]" by cjson,
// so this must be handled separately to prevent unexpected diff results.
nodes: !isEmpty(upstream.nodes) ? upstream.nodes : [],

checks: upstream.checks,
discovery_type: upstream.discovery_type,
service_name: upstream.service_name,
discovery_args: upstream.discovery_args,

...(upstream.nodes
? {
// Empty Lua tables will be encoded as "{}" rather than "[]" by cjson,
// so this must be handled separately to prevent unexpected diff results.
nodes: !isEmpty(upstream.nodes) ? upstream.nodes : [],
}
: {}),
});
return {
services:
Expand Down
Loading