Remove JFrog CLI server configurations

jf config rm (remove) deletes one or all server entries from your local JFrog CLI configuration. Removing a server clears stored credentials for that ID; omitting the server ID removes every configured server. Use --quiet to skip the confirmation prompt in an interactive terminal.

This topic covers:

Synopsis

jf config rm <server-id>

Aliases: jf c rm

Where:

  • <server-id>: Optional. When provided, only that server is removed. When omitted, all servers are removed. Append flags such as --quiet as needed.

Arguments

ArgumentRequiredDescription
server-idNoRemove only this server. Omit to remove all

Options

FlagDefaultDescription
--quietfalseSkip the interactive confirmation prompt. Only applies when running in an interactive terminal (TTY). In scripts and CI/CD pipelines the prompt is suppressed automatically, so this flag is not required there.

Examples

Remove a Specific Server

To remove a specific server:

  1. Run:

    jf config rm <server-id> --quiet

    Where:

    • <server-id>: The ID of the server to remove.

    For example:

    jf config rm staging-server --quiet
  2. Confirm the configuration. No output is printed on success. To verify the removal:

    • Run:

      jf config show

Remove All Servers

To remove all configured servers:

  1. Run:

    jf config rm --quiet
  2. Confirm that no servers remain. No output is printed on success. To verify all configurations are gone:

    • Run:

      jf config show

      Expected: empty output (no servers configured).

Recover After Removing the Active Server

If you removed the currently active server, another server must become the default before CLI commands target a platform.

To set a different server as the active default:

  • Run:

    jf config use <other-server-id>

    Where:

    • <other-server-id>: A server ID that remains in your configuration.

    For example:

    jf config use dev-server

Important Notes

  • Destructive action: Removing a server configuration deletes its stored credentials permanently. You cannot undo this. After removing, run jf config show to confirm the expected servers are no longer listed.
  • Remove all: Omitting the server ID removes all stored configurations. The --quiet flag skips the confirmation prompt in interactive terminal sessions. In CI/CD pipelines and non-interactive scripts, the prompt is suppressed automatically regardless of --quiet.
  • Active server: If you remove the active (default) server, there is no active server until you run jf config use <other-id> or add a new one with jf config add.
  • CI/CD cleanup: In pipelines, add jf config rm <server-id> --quiet as a teardown step to avoid leaking credentials in ephemeral environments.
  • Non-existent server ID: If the specified server-id does not exist, the CLI prints an informational message and exits 0. Confirm your server ID with jf config show before running remove in automation scripts.
  • Empty output after remove all: After removing all servers, jf config show returns empty output with exit code 0. This is expected — it does not indicate an error.

What’s Next

To configure a new server, see jf config add.