jfrog / jfrog/jfrog-cli-artifactory
Supports only triggering Export and not triggering download for Export release bundle v2 command "jf rbe"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 12
- Forks
- 49
- Avg merge
- 5d 16h
- Merged PRs (30d)
- 13
Description
Feature Description:
Currently, according to the info of "jf rbe --help":
"jf rbe - Triggers the Export process and downloads the Release Bundle archive"
When we try to export Release Bundle v2 using the command "jf rbe", these files are also downloaded, like:
$ jf rbe myApp2 1.0.0
08:37:10 [🔵Info] Exporting Release Bundle archive...
08:37:22 [🔵Info] [Thread 2] Downloading "release-bundles-v2/myApp2/1.0.0/myApp2-1.0.0.zip" to "myApp2/1.0.0/myApp2-1.0.0.zip"
08:37:22 [🔵Info] Successfully Downloaded Release Bundle archive
Expectation:
Only trigger the exporting of the Release bundle v2 through "jf rbe" without downloading.
The scenario is:
We only need to trigger the function of generating a download link on the UI for Release Bundle v2, and then send the download link to others.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the implementation and help text for the jf rbe command, then run jf rbe myApp2 1.0.0 to trace where exporting leads to archive downloading. Compare the command's behavior with the expectation that it only triggers Release Bundle v2 export and does not download the archive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100