riccardom 042c1839f5 [management] Cover the debug upload destination in the network-map drift guard ...

The drift guard asserts that the full, envelope and legacy paths produce the
same PeerConfig for a fixture. The new destination field was invisible to it:
the frozen legacy implementation never emitted it, so a fixture with a non-empty
account URL would have made legacy disagree with the other two, and no fixture
set one, so nothing failed and the field had no coverage at all.

The legacy path now emits the account setting, which is what AddressV6 already
does. It does not take the deployment-wide default the live path falls back to,
because the harness runs that path with no server config, so the two agree on
every fixture.

The dns-config case pins an account-level URL. Removing the legacy line makes it
fail on the legacy mode for that exact field, which is what makes the fixture
worth having.

2026-10-09 11:50:32 +02:00

..

controllers/network_map

[management] Cover the debug upload destination in the network-map drift guard

2026-10-09 11:50:32 +02:00

modules

[management] Refresh only affected peers on DNS zone and record changes (#8050)

2026-10-05 12:48:53 +02:00

network_map_db

[management,client] Take the debug-bundle upload destination from management

2026-09-10 16:38:41 +02:00

server

Merge remote-tracking branch 'origin/main' into fix_debug_upload_url_from_mgmt

2026-10-09 11:13:57 +02:00

shared

Merge remote-tracking branch 'origin/main' into fix_debug_upload_url_from_mgmt

2026-10-09 11:13:57 +02:00