Skip to content

Conversation

@gschueler
Copy link
Member

@gschueler gschueler commented Nov 18, 2024

request:

ER to make the included syntax of RD CLI consistent.

The "include" syntax differs between export and import, even if you're including the same configurations.

Eg:

$ rd projects archives import help

Import a project archive

Usage: import options
--file -f value : Output file path
[--include-acl -a] : Include ACLs in import, default: false
[--include-config -c] : Include project configuration in import, default: false
[--include-scm -s] : Include SCM configuration in import, default: false (api v28 required)
[--noExecutions -x] : Do not include executions in import. Default: do include executions in import.
[--project -p /^[-_a-zA-Z0-9+][-._a-zA-Z0-9+]*$/] : Project name
[--remove -r] : Remove Job UUIDs in imported jobs. Default: preserve job UUIDs.
[--strict] : Return non-zero exit status if any imported item had an error. Default: only job import errors are treated as failures.

$ rd projects archives export help

export a project archive

Usage: export options
[--execids -e value...] : List of execution IDs. Exports only those ids.
--file -f value : Output file path
[--include -i value...] : List of archive contents to include. [all,jobs,executions,configs,readmes,acls,scm]. Default: all. (API v19 required for other options).
[--project -p /^[-_a-zA-Z0-9+][-._a-zA-Z0-9+]*$/] : Project name

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants