-
Why are the DevOps organization and project names required when the $ gh actions-importer dry-run azure-devops pipeline --source-file-path ./path/to/azure-pipelines-pr.yml --features ghes-latest --no-telemetry -o ./workflows
[2023-03-05 20:57:53] No value provided for the required options '--azure-devops-organization, --azure-devops-project'
[2023-03-05 20:57:53] Logs: './log/valet-20230305-205753.log'
Why are credentials required for
$ gh actions-importer dry-run azure-devops pipeline --source-file-path ./path/to/azure-pipelines-pr.yml --features ghes-latest --no-telemetry -o ./workflows -g ORG_NAME -p PROJECT_NAME
[2023-03-05 20:59:14] Unable to locate credentials for 'https://github.com'
[2023-03-05 20:59:14] Logs: './workflows/log/valet-20230305-205914.log'
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi jritus, Unfortunately right now the cli do not discriminate for which command you are running (audit vs dry run for example), hence we cannot make cli options conditional and they are required today. With regards to the azure devops required arguments, they are required and used to construct the output filepath. You can use a placeholder for that if supplying actual values is not possible right now. |
Beta Was this translation helpful? Give feedback.
Hi jritus,
Unfortunately right now the cli do not discriminate for which command you are running (audit vs dry run for example), hence we cannot make cli options conditional and they are required today.
With regards to the azure devops required arguments, they are required and used to construct the output filepath. You can use a placeholder for that if supplying actual values is not possible right now.