Is your feature request related to a problem? Please describe.
Feature:
There are users/customers that would like to use the JFrog CLI but have restrictions with creating configuration files or even saving credentials in them.
users credentials should be used (each team has service user)
for security reason they don’t want to store credentials in config files on Agents VMs
they don’t use Artifactory to store docker images because they have another repository
Artifactory plugin is incompatible with latest Bamboo Data Center version so they can’t use it
The problem is that this doesn't work:
jf docker scan –url=’’ --user=’’ --password=’
The issue is that the --url and the credentials can only be passed through a service-id configuration file.
Describe the solution you'd like to see
We would like to be able to support the above credentials to this command and other package types as well.
Describe alternatives you've considered
The current workaround is to first save the docker image as a .tar file (using docker save command) and then scan the tar with jf scan and this command is supported with credentials and url.
Is your feature request related to a problem? Please describe. Feature: There are users/customers that would like to use the JFrog CLI but have restrictions with creating configuration files or even saving credentials in them. users credentials should be used (each team has service user) for security reason they don’t want to store credentials in config files on Agents VMs they don’t use Artifactory to store docker images because they have another repository Artifactory plugin is incompatible with latest Bamboo Data Center version so they can’t use it
The problem is that this doesn't work: jf docker scan –url=’’ --user=’’ --password=’
The issue is that the --url and the credentials can only be passed through a service-id configuration file.
Describe the solution you'd like to see We would like to be able to support the above credentials to this command and other package types as well.
Describe alternatives you've considered The current workaround is to first save the docker image as a .tar file (using docker save command) and then scan the tar with jf scan and this command is supported with credentials and url.