jfrog
Access to calling curl through JF CLI based on the JFrog Platform URL
Is your feature request related to a problem? Please describe. Currently, the JFrog CLI allows us to perform a number of tasks to maintain the JFrog Platform and the associated applications having the credentials stored away safely.
However not all services which are provided through the REST API which are also fully accessible through the JFrog CLI. This may result in credential information being leaked through build pipeline logs if the REST API's are invoked and insufficient care is given ir order to avoid presenting the information.
Examples of this are that it is possible to create new release bundles, but getting a list of existing release bundles require The REST API's to be called directly.
Describe the solution you'd like to see I would like to be able to call the REST API from the JFrog CLI based on the JFrog Platform URL instead of being restricted to do so based on the "jf rt curl..." and the "jf xr curl..." which limit which endpoints are available.
An example of this could be: jf curl -XPOST "/lifecycle/api/v2/promotion...
Describe alternatives you've considered The alternatives would be to either be limited by which commands have been implemented in the JFrog CLI, or to using the JFrog REST API specifying credentials directly and hoping no credentials are leaked into the build logs.
This issue has been marked as stale due to 6 months of inactivity. As part of our effort to address every issue properly, please feel free to remove the stale label or keep this issue active by leaving a comment. Otherwise, it will be closed in 7 days
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
We do not plan to support this. In order to make it work, create a token with the CLI and then use that token for regular curl calls.
We do not plan to support this. In order to make it work, create a token with the CLI and then use that token for regular curl calls.
Can you elaborate on the reason you're not going to support it? You already support the feature for jfrog rt curl and jfrog xr curl, it seems strange to limit this very useful feature to a relatively small subset of API endpoints.