mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-02-05 08:18:06 +00:00
Currently, the logging for which resources get activated and de-activated is spread between the `dns` and `client` module. It also doesn't include the sites that the resource is defined in. The name of a resource alone is not enough to unique identify it. To fix both of these papercuts, we move the logging to the `client` module and include the sites in the log message. The log messages now read like this: ``` 2024-08-12T02:26:01.477844Z INFO firezone_tunnel::client: Activating resource name=IPerf3 address=10.0.32.101/32 sites=AWS Dev (Gateways track `main`) 2024-08-12T02:26:01.477904Z INFO firezone_tunnel::client: Activating resource name=*.slack.com address=*.slack.com sites=Vultr Stable (Latest Release Gateways) 2024-08-12T02:26:01.477942Z INFO firezone_tunnel::client: Activating resource name=*.slack-edge.com address=*.slack-edge.com sites=Vultr Stable (Latest Release Gateways) 2024-08-12T02:26:01.477984Z INFO firezone_tunnel::client: Activating resource name=*.spotify.com address=*.spotify.com sites=AWS Dev (Gateways track `main`) ```
Connlib
Firezone's connectivity library shared by all clients.
Building Connlib
You shouldn't need to build connlib directly; it's typically built as a dependency of one of the other Firezone components. See READMEs in those directories for relevant instructions.