Cover the four scenarios the fix addresses end-to-end via stream
sockets: service status disable, re-enable, deletion, and recreation.
Each asserts that route matching reflects the new service state once
the rebuild path runs.

Ports the test file from api7-ee apache#1417 (the source PR for this
backport) which was omitted from the initial port.

* fix: rebuild stream router when services change

* test: add integration tests for stream router rebuild on service change

Cover the four scenarios the fix addresses end-to-end via stream
sockets: service status disable, re-enable, deletion, and recreation.
Each asserts that route matching reflects the new service state once
the rebuild path runs.

Ports the test file from api7-ee #1417 (the source PR for this
backport) which was omitted from the initial port.

* fix: skip stream routes whose service is missing or disabled

The previous commit started rebuilding the stream router whenever
services.conf_version changes, but the rebuild produced the same
routing decisions because create_router() didn't actually consult
service status — service_fetch wasn't even imported in this file.

Add the missing service_id enforcement at the top of the iteration
loop:

  - If a stream_route references a service_id whose service can't be
    fetched (deleted, or not yet synced from etcd), log
    'failed to fetch service configuration by id: <id>' and skip
    the route.
  - If the service status is 0 (explicitly disabled), skip the route.

Combined with the conf_version trigger from the previous commit, a
service status flip / delete / late-sync now propagates into routing
decisions on the next match() call.

This is what the integration tests added in
t/stream-node/service-change-rebuild-router.t exercise; without this
patch, TESTs 2-4 fail because the disabled / deleted service is
ignored at routing time.

Signed-off-by: Abhishek Choudhary <[email protected]>

* refactor(stream-router): drop unreachable service lookup in rebuild

Apisix admin guarantees stream_routes' referenced services exist
(referenced services cannot be deleted), and the services schema does
not expose a status field, so there is no actionable outcome from a
per-route service fetch. Rebuilding on services.conf_version is enough.

Refocus the integration test on what apisix exposes: update the bound
service and verify routing continues to match through the
conf_version-driven rebuild.

---------

Signed-off-by: Abhishek Choudhary <[email protected]>

* fix: rebuild stream router when services change

* test: add integration tests for stream router rebuild on service change

Cover the four scenarios the fix addresses end-to-end via stream
sockets: service status disable, re-enable, deletion, and recreation.
Each asserts that route matching reflects the new service state once
the rebuild path runs.

Ports the test file from api7-ee apache#1417 (the source PR for this
backport) which was omitted from the initial port.

* fix: skip stream routes whose service is missing or disabled

The previous commit started rebuilding the stream router whenever
services.conf_version changes, but the rebuild produced the same
routing decisions because create_router() didn't actually consult
service status — service_fetch wasn't even imported in this file.

Add the missing service_id enforcement at the top of the iteration
loop:

  - If a stream_route references a service_id whose service can't be
    fetched (deleted, or not yet synced from etcd), log
    'failed to fetch service configuration by id: <id>' and skip
    the route.
  - If the service status is 0 (explicitly disabled), skip the route.

Combined with the conf_version trigger from the previous commit, a
service status flip / delete / late-sync now propagates into routing
decisions on the next match() call.

This is what the integration tests added in
t/stream-node/service-change-rebuild-router.t exercise; without this
patch, TESTs 2-4 fail because the disabled / deleted service is
ignored at routing time.

Signed-off-by: Abhishek Choudhary <[email protected]>

* refactor(stream-router): drop unreachable service lookup in rebuild

Apisix admin guarantees stream_routes' referenced services exist
(referenced services cannot be deleted), and the services schema does
not expose a status field, so there is no actionable outcome from a
per-route service fetch. Rebuilding on services.conf_version is enough.

Refocus the integration test on what apisix exposes: update the bound
service and verify routing continues to match through the
conf_version-driven rebuild.

---------

Signed-off-by: Abhishek Choudhary <[email protected]>