Delete a permission target with jf rt permission-target-delete

Permanently delete a permission target from the JFrog Platform.

Prerequisites

• JFrog CLI installed and configured (jf config add)
• Admin privileges on the Artifactory instance
• An existing permission target to delete. To create one, see jf rt permission-target-create

Synopsis

jf rt permission-target-delete <permission-target-name> [options]

Aliases: rt ptdel

📘

Note

The CLI --help output displays the alias form (jf rt ptdel) as the command name. Both permission-target-delete and ptdel are fully equivalent.

Arguments

Options

Examples

Delete a Permission Target (Interactive)

Run without --quiet in a terminal to see a confirmation prompt before deletion.

To delete a permission target interactively:

1. Run:

jf rt permission-target-delete <permission-target-name>

Where:

• <permission-target-name> — name of the permission target to remove (see Arguments).

Full example:

jf rt permission-target-delete my-permission-target

Expected output:

[Info] Deleting permission target...
Delete the permission target 'my-permission-target'? (y/N): y
[Info] Done deleting permission target.

Enter y to confirm or N (or press Enter) to cancel without making any changes.

🚧

Warning

This action permanently removes the permission target. You cannot undo it.

Delete a Permission Target (Non-Interactive)

Use --quiet to suppress the confirmation prompt — required for CI pipelines and scripts.

To delete a permission target without a confirmation prompt:

1. Run:

jf rt permission-target-delete <permission-target-name> --quiet

Full example:

jf rt permission-target-delete my-permission-target --quiet

Expected output:

[Info] Deleting permission target...
[Info] Done deleting permission target.

🚧

Warning

This action permanently removes the permission target. You cannot undo it.

Delete a Permission Target That Does Not Exist

If the named permission target is not found, the command exits with code 1 and prints an error.

To handle a missing permission target (example):

1. Run:

jf rt permission-target-delete <permission-target-name> --quiet

Full example:

jf rt permission-target-delete nonexistent-target --quiet

Expected output:

[Info] Deleting permission target...
[Error] server response: 404
{"errors":[{"status":404,"message":"Permission target 'nonexistent-target' does not exist"}]}

Use the exit code in scripts to detect this condition:

Full example:

jf rt permission-target-delete my-target --quiet
if [ $? -ne 0 ]; then
  echo "Delete failed — target may not exist"
fi

View command usage

To view command usage:

1. Run:

jf rt permission-target-delete --help

Expected output:

Name:
  jf rt ptdel - Permanently delete a permission target.

Usage:
  jf rt ptdel <permission target name>

Arguments:
  permission target name
    Specifies the permission target that should be removed.

Options:
  --quiet    [Default: $CI] Set to true to skip the delete confirmation message.
  ...

Important Notes

• Irreversible: Deleting a permission target immediately removes access control rules. Users and groups governed by this target lose their permissions instantly.
• --quiet default: Defaults to true when the CI environment variable is set to any non-empty value. In non-interactive environments (piped stdin in scripts), the confirmation prompt is also skipped automatically even without setting --quiet or $CI. To unconditionally suppress the prompt, pass --quiet=true explicitly.
• Confirmation prompt: In an interactive terminal (without --quiet), the CLI asks:

  Delete the permission target '<name>'? (y/N):

  Enter y to proceed or N to abort. The deletion is not performed until you confirm.
• Requires admin privileges on the Artifactory instance.
• If the permission target does not exist, the command exits with code 1 and returns a 404 server error. See the example above for the exact error format.
• The CLI emits [Info] Deleting permission target... immediately before contacting the server. If an error follows this line, the deletion did not occur.
• The error response includes a Trace ID in an [Info] line preceding the error. Provide this ID when raising a support ticket.

Related Commands