Authentication failure when adding SSH server configuration

[gpwen]

Describe the bug

It seemed somewhere between version 2.71.1 and 2.72.2, jfrog CLI starts to authenticate with server when adding a SSH server configuration:

jf.exe config add "server-id" --interactive=false --url "ssh://server.com:1339"

That command will fail if the private SSH key has not been loaded.

The change makes it quite difficult to add large amount of server configuration (I have tens of different servers to add). It also makes it impossible to simply create a configuration file that can be deployed to production environment. The account that creates the configuration file is not necessarily the account that uses it. Therefore, authentication may indeed won't work when adding server configurations.

Is it possible to add an option to disable such behavior? Or revert back to the old behavior?

Thanks!

Current behavior

When executing the following command with JFrog CLI version 2.72.2:

jf.exe config add "server-id" --interactive=false --url "ssh://server.com:1339"

The following error will be reported:

[🚨Error] Authentication via SSH key failed.

That command used to work correctly in version 2.71.1.

Reproduction steps

Execute the following command:

jf.exe config add "server-id" --interactive=false --url "ssh://server.com:1339"

Expected behavior

The config command finishes correctly without error.

JFrog CLI version

2.72.2

Operating system type and version

Windows 11 23H2

JFrog Artifactory version

Enterprise Plus 7.77.12 rev 77712900

JFrog Xray version

Unknown