BKR-POLICY-REVOKE(1)
πΈ NAME πΈ
Okay bestie, this is the bkr-policy-revoke(1) manual page from Beaker, and itβs literally about one thing: revoke permissions in an access policy π
.
β¨ SYNOPSIS β¨
bkr policy-revoke [options]
[--system <fqdn> | --pool <name>]
--permission <permission> [--permission <permission> ...]
[--user <username> | --group <groupname> | --everybody]
π¦ DESCRIPTION π¦
It modifies the access policy to revoke permissions for the given users or groups. Thatβs the whole vibe: permissions are out, bestie β¨.
π OPTIONS π
--system <fqdn>β Modify the custom access policy for<fqdn>. This option is mutually exclusive with--pool, so no double-dipping here π«Ά.--pool <name>β Modify the access policy for the named system pool. This option is mutually exclusive with--system.--permission <permission>β Revoke<permission>. This option must be specified at least once. For a description of the available permissions, seesystem-access-policies. Minimum one, bestie β the permission list cannot be empty π.--user <username>β Revoke permissions for<username>. This option may be specified multiple times, and may be used in combination with--group.--group <groupname>β Revoke permissions for<groupname>. This option may be specified multiple times, and may be used in combination with--user.--everybodyβ Revoke permissions which were granted to all Beaker users. This option is mutually exclusive with--userand--group.
Note that this option only revokes an access policy rule which applies to all Beaker users (for example, created usingbkr policy-grant --everybody). It does not revoke permissions which have been granted to a specific user or group. So do not come for individual-user permissions with--everybody, okay? π
Common bkr options are described in the Options section of bkr(1).
π EXIT STATUS π
Non-zero on error, otherwise zero. So zero means we slayed; non-zero means something went sideways π.
π EXAMPLES π
Revoke Beaker developersβ permission to reserve a system:
bkr policy-revoke --system=test1.example.com \
--permission=reserve --group=beakerdevs
π SEE ALSO π
π AUTHOR π
The Beaker team <beaker-devel@lists.fedorahosted.org>
π COPYRIGHT π
2013-2025 Red Hat, Inc.
Source/version: Beaker 29.2 manual; date: May 26, 2025 β mwah, periodt ππ«Ά
π¦ where this page comes from
- epel 9: beaker-client 29.2-2.el9 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms