diff options
| author | Nick Khyl <nickk@tailscale.com> | 2025-05-14 11:57:01 -0500 |
|---|---|---|
| committer | Nick Khyl <1761190+nickkhyl@users.noreply.github.com> | 2025-05-14 17:58:16 -0500 |
| commit | 824985afe1767c49a1337974cfeceaa07ad8fdbd (patch) | |
| tree | ad2240546346a36bfdcf5ee6ffdfbdf3fc6d9d5f /control/controlhttp/controlhttpserver | |
| parent | 49a7685af95a6105f9818d69fcc8ce2440ece67f (diff) | |
| download | tailscale-824985afe1767c49a1337974cfeceaa07ad8fdbd.tar.xz tailscale-824985afe1767c49a1337974cfeceaa07ad8fdbd.zip | |
feature/taildrop,ipn/ipn{ext,local}: initialize taildrop for initial profile
Currently, LocalBackend/ExtensionHost doesn't invoke the profile change callback for the initial profile.
Since the initial profile may vary depending on loaded extensions and applied policy settings,
it can't be reliably determined until all extensions are initialized. Additionally, some extensions
may asynchronously trigger a switch to the "best" profile (based on system state and policy settings) during
initialization.
We intended to address these issues as part of the ongoing profileManager/LocalBackend refactoring,
but the changes didn't land in time for the v1.84 release and the Taildrop refactoring.
In this PR, we update the Taildrop extension to retrieve the current profile at initialization time
and handle it as a profile change.
We also defer extension initialization until LocalBackend has started, since the Taildrop extension
already relies on this behavior (e.g., it requires clients to call SetDirectFileRoot before Init).
Fixes #15970
Updates #15812
Updates tailscale/corp#28449
Signed-off-by: Nick Khyl <nickk@tailscale.com>
Diffstat (limited to 'control/controlhttp/controlhttpserver')
0 files changed, 0 insertions, 0 deletions