Victor Lyuboslavsky ae1f846739 Switched to lighter weight authz unit tests for activity bounded context. (#38735) ... <!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #38234 This came up in activity bounded context code review. Following existing patterns, authz testing will be in `policy_test.go`, and integration tests will simply cover connectivity (not exhaustive authz). <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Tests** * Enhanced authorization test coverage for activity operations with improved validation scenarios. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->		2026-01-26 11:20:21 -06:00
..
authz.go	Activity bounded context: /api/latest/fleet/activities (1 of 2) (#38115)	2026-01-19 09:07:14 -05:00
errors.go	Activity bounded context: /api/latest/fleet/activities (1 of 2) (#38115)	2026-01-19 09:07:14 -05:00
policy.rego	Global observers and maintainers can now officially read user details (#38558)	2026-01-21 13:55:10 -06:00
policy_test.go	Switched to lighter weight authz unit tests for activity bounded context. (#38735)	2026-01-26 11:20:21 -06:00
policy_test.rego	Add authorization checks in service (#938)	2021-06-03 16:24:15 -07:00