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--quietas needed.
Arguments
| Argument | Required | Description |
|---|---|---|
server-id | No | Remove only this server. Omit to remove all |
Options
| Flag | Default | Description |
|---|---|---|
--quiet | false | Skip 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:
-
Run:
jf config rm <server-id> --quietWhere:
<server-id>: The ID of the server to remove.
For example:
jf config rm staging-server --quiet -
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:
-
Run:
jf config rm --quiet -
Confirm that no servers remain. No output is printed on success. To verify all configurations are gone:
-
Run:
jf config showExpected: 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 showto confirm the expected servers are no longer listed. - Remove all: Omitting the server ID removes all stored configurations. The
--quietflag 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 withjf config add. - CI/CD cleanup: In pipelines, add
jf config rm <server-id> --quietas a teardown step to avoid leaking credentials in ephemeral environments. - Non-existent server ID: If the specified
server-iddoes not exist, the CLI prints an informational message and exits 0. Confirm your server ID withjf config showbefore running remove in automation scripts. - Empty output after remove all: After removing all servers,
jf config showreturns empty output with exit code 0. This is expected — it does not indicate an error.
Updated 13 days ago
