Lucas Manuel Rodriguez ed4f6e4178 Remove old mdm_command action (do we really need it?) (#11222) ... A question in form of PR: Do we really need the following two entities in our [policy.rego](https://github.com/fleetdm/fleet/blob/main/server/authz/policy.rego) `1. (object=mdm_apple_command, action=read/write)` and `2. (object=host, action=mdm_command)`? (Maybe mdm_command is a leftover action from the PoC?) Guess: `mdm_apple_command` (`fleet.MDMAppleCommandAuthz`) is what we want: `action=write` means you can enqueue, `action=read` means you can list commands and read their results. PS: Found this while trying to add command execution permissions to the new `GitOps` role.		2023-04-18 07:53:33 -03:00
..
authz.go	Bump go to 1.19.1 (#7690)	2022-09-12 20:32:43 -03:00
errors.go	Add UUID to Fleet errors and clean up error msgs (#10411)	2023-03-13 13:44:06 -03:00
policy_test.go	Remove old mdm_command action (do we really need it?) (#11222)	2023-04-18 07:53:33 -03:00
policy_test.rego	Add authorization checks in service (#938)	2021-06-03 16:24:15 -07:00
policy.rego	Remove old mdm_command action (do we really need it?) (#11222)	2023-04-18 07:53:33 -03:00