BKR-POLICY-GRANT(1)

📦
version 29.2 · 3 versions
, in epel 9

💅 bkr-policy-grant — the Beaker manual, bestie edition ✨

Okay so real talk: bkr-policy-grant is a page from the Beaker manual (that's the manual name, iykyk) and it's literally the "let people in" command 🎀. It lets you hand out permissions in an access policy. No cap.

✨ NAME ✨

bkr-policy-grant — grant permissions in an access policy 👑

🌸 SYNOPSIS 🌸

bkr policy-grant [options]
  [--system <fqdn> | --pool <name>]
  --permission <permission> [--permission <permission> ...]
  [--user <username> | --group <groupname> | --everybody]

🦋 DESCRIPTION 🦋

So what does it do? It modifies the access policy to grant shiny new permissions to the users or groups you name. That's it, that's the whole vibe. Give people the keys 🔑.

💖 OPTIONS 💖

  • --system <fqdn> — modify the custom access policy for <fqdn>. Heads up bestie: this option is mutually exclusive with --pool. Pick one, not both, fr fr.
  • --pool <name> — modify the access policy for the named system pool. And yep, this one is mutually exclusive with --system. The drama of it all 💀.
  • --permission <permission> — grant <permission>. You must specify this at least once — no permission, no party. For a description of all the available permissions, go look at system-access-policies.
  • --user <username> — grant permissions to <username>. You can stack this option multiple times 🫶 and you can totally use it in combination with --group.
  • --group <groupname> — grant permissions to <groupname>. Also stackable, multiple times, and it plays nice in combination with --user 💜.
  • --everybody — grant permissions to all Beaker users. Iconic, generous, chaotic. This one is mutually exclusive with --user and --group — you can't do everybody and specific people, pick a lane 🌈.

Oh and the common bkr options? Those are described in the Options section of bkr(1). Go check it if you're curious ✨.

🎀 EXIT STATUS 🎀

Non-zero if something went wrong, otherwise zero. Simple as that 💅.

⭐ EXAMPLES ⭐

Wanna grant the Beaker developers permission to reserve a system? Slay, here's how:

bkr policy-grant --system=test1.example.com \
    --permission=reserve --group=beakerdevs

🌈 SEE ALSO 🌈

bkr(1), bkr-policy-revoke(1)

👑 AUTHOR 👑

The Beaker team <beaker-devel@lists.fedorahosted.org> — the main characters, honestly.

2013-2025 Red Hat, Inc.

That's the whole page bestie, go forth and grant permissions responsibly 💖🧚✨

Written for version 29.2, dated May 26, 2025 — that's the Beaker release tag and the page date, noted here with love 💜🫶🎀

📦 where this page comes from