Kristoffer Dalby 21e3f2598d policy: fix issue where non existent user results in empty ssh pol ... When we encounter a source we cannot resolve, we skipped the whole rule, even if some of the srcs could be resolved. In this case, if we had one user that exists and one that does not. In the regular policy, we log this, and still let a rule be created from what does exist, while in the SSH policy we did not. This commit fixes it so the behaviour is the same. Fixes #2863 Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>		2025-11-10 20:34:12 +01:00
..
matcher	matcher: Add func for comparing Dests and TheInternet	2025-11-02 13:19:59 +01:00
policyutil	policy: fix autogroup:self propagation and optimize cache invalidation (#2807)	2025-10-23 17:57:41 +02:00
v2	policy: fix issue where non existent user results in empty ssh pol	2025-11-10 20:34:12 +01:00
pm.go	policy: fix autogroup:self propagation and optimize cache invalidation (#2807)	2025-10-23 17:57:41 +02:00
policy_autoapprove_test.go	state/nodestore: in memory representation of nodes	2025-09-09 09:40:00 +02:00
policy_route_approval_test.go	state/nodestore: in memory representation of nodes	2025-09-09 09:40:00 +02:00
policy_test.go	policy: reproduce 2863 in test	2025-11-10 20:34:12 +01:00
policy.go	policy: fix autogroup:self propagation and optimize cache invalidation (#2807)	2025-10-23 17:57:41 +02:00
route_approval_test.go	state/nodestore: in memory representation of nodes	2025-09-09 09:40:00 +02:00