BKR-POLICY-REVOKE(1)

πŸ“¦
version 29.2 Β· 3 versions
, in epel 9

🌸 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, see system-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 --user and --group.
Note that this option only revokes an access policy rule which applies to all Beaker users (for example, created using bkr 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 🌈

bkr(1), bkr-policy-grant(1)

πŸŽ€ AUTHOR πŸŽ€

The Beaker team <beaker-devel@lists.fedorahosted.org>

2013-2025 Red Hat, Inc.

Source/version: Beaker 29.2 manual; date: May 26, 2025 β€” mwah, periodt πŸ’‹πŸ«Ά

πŸ“¦ where this page comes from