Add --export-only flag to jf rbe command

[JFrog-MengKe]

Add --export-only flag to jf rbe command

Summary

This PR adds a new --export-only flag to the jf rbe (release-bundle-export) command, allowing users to trigger the export process without waiting for the download to complete.

Problem

Currently, the jf rbe command always waits for the export process to complete and then downloads the bundle file. In some scenarios, users may want to:

• Trigger the export process asynchronously
• Monitor the export status separately
• Download the bundle at a later time

Solution

• Added --export-only boolean flag to the rbe command
• When --export-only is set to true, the command only triggers the export process and returns immediately
• When --export-only is false (default), the command maintains the existing behavior (export + download)
• Added corresponding ExportReleaseBundleOnly method in the lifecycle service

Changes Made

jfrog-client-go

• lifecycle/services/export.go: Added ExportReleaseBundleOnly method that triggers export without waiting
• lifecycle/manager.go: Added corresponding manager method

jfrog-cli-artifactory

• cliutils/flagkit/flags.go: Added ExportOnly flag definition and command flags mapping
• lifecycle/commands/export.go:
  • Added exportOnly field to ReleaseBundleExportCommand struct
  • Modified Run() method to conditionally call export-only or full export+download
  • Added SetExportOnly() method
• lifecycle/cli.go: Updated export command to pass the --export-only flag value
• lifecycle/docs/export/help.go: Updated command description to mention the new flag

Usage Examples

# Original behavior (export + download)
jf rbe my-bundle 1.0.0 ./download-path

# New behavior (export only, no download)
jf rbe my-bundle 1.0.0 ./download-path --export-only

Testing

• Command help shows the new --export-only flag
• Flag is properly parsed and passed to the command logic
• Export-only mode triggers export without waiting for download
• Default behavior (without flag) remains unchanged

Backward Compatibility

This change is fully backward compatible. The default behavior remains unchanged, and the new flag is optional.

Related Issues

Fixes the requirement to add export-only functionality to release bundle export command.

Sign CLA

I have read the CLA Document and I hereby sign the CLA

recheck

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[github-actions]

---

🐸 JFrog Frogbot

[JFrog-MengKe]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

recheck