mlsmaycon 30ca6a9809 [management] Return agent-network settings defaults before bootstrap ...

Settings endpoints elsewhere in the API always answer with a JSON object:
account settings rows are created with the account and DNS settings live
on it with zero-value defaults. Agent-network settings deviated because
the row is created lazily at bootstrap (cluster is a deployment choice and
the subdomain must be generated uniquely per cluster), and GetSettings
passed the store's not-found straight through to the wire.

The manager now synthesises the defaults on read when no row exists yet,
without persisting: log collection on with the default retention, and an
empty cluster, subdomain and endpoint as the not-bootstrapped signal. The
timestamps stay off the wire until a row is written. Bootstrap persists
the same defaults, so the pre-bootstrap view and the freshly bootstrapped
row agree.

2026-08-02 04:20:59 +00:00

..

client

[management] Return agent-network settings defaults before bootstrap

2026-08-02 04:20:59 +00:00

domain

[management] Streamline domain validation (#5211)

2026-01-29 13:51:44 +01:00

grpc

[client, management] offload client config generation to the client (#6711)

2026-07-22 18:20:27 +02:00

http

[management] Return agent-network settings defaults before bootstrap

2026-08-02 04:20:59 +00:00

networkmap

[management] component types (#6866)

2026-07-23 11:37:09 +02:00

operations

[client,management] Rewrite the SSH feature (#4015)

2025-11-17 17:10:41 +01:00

proto

[client, management] offload client config generation to the client (#6711)

2026-07-22 18:20:27 +02:00

status

[management,proxy,client] 0.74.0 version (#6563)

2026-07-01 12:45:14 +02:00

types

[management] Force routing-peer DNS resolution for reverse-proxy domain targets (#6872)

2026-07-28 14:45:57 +02:00